Sun May 28 10:45:51 PDT 2006
- Previous message: [Slony1-general] Inheritance and slony
- Next message: [Slony1-general] Inheritance and slony
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sun, May 28, 2006 at 09:43:46AM -0700, Alan Hodgson wrote: > On Saturday 27 May 2006 19:26, elein <elein at varlena.com> wrote: > > I've got a customer with tons of inherited tables. > > Is there any reason why slony-I does not work with > > inheritance? I thought I heard that, but would like > > very much to believe it is not true. > > > > Anything I should watch out for with inheritance and slony-I > > if it does work? > > The only problem I've seen doing this is sometimes the column ordering gets > out of whack depending when you add them on the master vs. copying the > schema to the slave(s). > > This shouldn't be a problem now that Slony specifies the column ordering > during COPY, though. I haven't had any problems since that was changed. > Good to know! Any other gotchas anyone has run into may be helpful. If it looks good, I am going to test on a wild schema with tons of child tables (not my design!) and will report back. Thank you all for perltools... --elein elein at varlena.com > -- > "Corruptissima republica, plurimae leges" (The more corrupt the state, > the more laws.) - Tacitus > > _______________________________________________ > Slony1-general mailing list > Slony1-general at gborg.postgresql.org > http://gborg.postgresql.org/mailman/listinfo/slony1-general >
- Previous message: [Slony1-general] Inheritance and slony
- Next message: [Slony1-general] Inheritance and slony
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list