Tue Sep 4 10:51:04 PDT 2007
- Previous message: [Slony1-general] Configuration on 2 sites
- Next message: [Slony1-general] missing sl_listen path following SUBSCRIBE SET
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 8/30/07, Jan Wieck <JanWieck at yahoo.com> wrote: > > On 8/30/2007 10:34 PM, Andrew Sullivan wrote: > > On Thu, Aug 30, 2007 at 08:11:25PM -0400, Jan Wieck wrote: > >> You forget that Slony is also supposed to replicate across different > >> Postgres versions. So what are we going to do if DDL with multiple > >> nesting layers of different comment styles is supported by one, but not > >> all Postgres versions inside of a Slony cluster? Somehow convert it to > >> something that is understood by all? > > > > No, we're supposed to support the least common denominator. If there > > isn't one, then I agree tha the user loses. This is more or less the > > pg_dump strategy: use the latest, or die. > > Which means we'd have to somehow extract the Postgres backend or psql > parser in order to do so. Without that I don't know how to keep the two > 100 percent in sync. > This seems to be the right direction to go in. An ideal solution would be a generalized parser that worked for the backend, psql (including tab completion), slony and other applications. I don't have any clever ideas on how to do that though. Andrew -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.slony.info/pipermail/slony1-general/attachments/20070904/= ac054a0c/attachment-0001.htm
- Previous message: [Slony1-general] Configuration on 2 sites
- Next message: [Slony1-general] missing sl_listen path following SUBSCRIBE SET
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list