On Wednesday, October 22, 2003, at 03:03 PM, Andrew Sullivan wrote:


On Wed, Oct 22, 2003 at 02:43:54PM -0400, Andrew Rawnsley wrote:

This is to announce an alternate fork/build of the eRServer 1.2 code base, provided to the community for testing purposes. If everything works out fine, and the Powers That Be approve, we can work on moving some of it to the main distribution. This is a first release, so be warned.

The patches are also in the "patch" area (assuming they're the same) of the erserver pages.

I'm a little leery of applying these, because as they are, they will
almost certainly break pre-7.3 systems.  What are people's feelings
about that?  Should we just accept that, as 7.2 is now officially
deprecated, we need not support it?


I wouldn't recommend applying them yet, either. I would like to let people kick the stuff around for a while. I
can't claim exhaustive testing on it, and don't want to embarrass myself too much...


Actually, it won't break pre-7.3 systems. I managed to pack it all into one distribution with a setup option for no schema support.
I have tested it against 7.3.4 and 7.2.4. Even 7.3.4 replicating to 7.2.4.



I'm cc:ing this to the pgsql-general list, because I think several
people who are trying out the code are not on this list.

A

--
----
Andrew Sullivan                         204-4141 Yonge Street
Afilias Canada                        Toronto, Ontario Canada
<[EMAIL PROTECTED]>                              M2P 2A8
                                         +1 416 646 3304 x110

_______________________________________________
Erserver-general mailing list
[EMAIL PROTECTED]
http://gborg.postgresql.org/mailman/listinfo/erserver-general

--------------------

Andrew Rawnsley
President
The Ravensfield Digital Resource Group, Ltd.
(740) 587-0114
www.ravensfield.com


---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly

Reply via email to