Wed Apr 25 13:47:29 PDT 2007
- Previous message: [Slony1-hackers] PostgreSQL 8.3 compatibility
- Next message: [Slony1-hackers] PostgreSQL 8.3 compatibility
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Darcy Buskermolen wrote: > On April 25, 2007 11:19 am, Dave Page wrote: > >> I've been looking at compatibility with 8.3 prior to building a demo of >> the new style windows installer for PostgreSQL that we're planning. I >> see that CVS head has an update to use VARATT_SIZEP_DEPRECATED instead >> of VARATT_SIZEP, however this change is obsolete already following >> Greg's recent work minimising the on disk size of various datatypes. >> >> Before I spend any time on this, is anyone else working on 8.3 >> compatibility? >> > > I'm not doing any current work, nor do i know of anybody else who is. > > Jan has some pretty big changes in mind, in view of 8.3 having the ability to shut off triggers/rules without needing to hack on pg_catalog. Jan needs to [pester, pester] start publishing the ideas on that. There's a "greater vision" there (and he needs to make the argument about this) that we should see about having "Slony-I 2.0" be a cleaner, gentler version of Slony-I that would work only on PG 8.3 (and above). Maintaining an upgrade path would mandate that Slony-I 1.2.x be compatible with PG 8.3, of course. Note that I have been doing some work on removing 7.3-isms, removing TABLE ADD KEY, and doing other code cleanup on CVS HEAD with a view to simplifying the code base somewhat in preparation for that. >> I'd also like to back port this to 1.2.x so we can release a build with >> PostgreSQL 8.3. Any objections? >> > > Well lets see the work commited to -HEAD first, and if it's not too obtrusive > then back patching to 1.2 may be applicable. > > Yes, that seems like a good idea. Some Windows-related changes came in from Hiroshi Saito in March; I have applied some of it, but found some of it wouldn't apply cleanly against CVS HEAD. If we can get some combination of Dave and Hiroshi (probably both) added to the committers list, then that should allow them to more cleanly address this.
- Previous message: [Slony1-hackers] PostgreSQL 8.3 compatibility
- Next message: [Slony1-hackers] PostgreSQL 8.3 compatibility
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-hackers mailing list