Tue May 24 19:35:21 PDT 2005
- Previous message: [Slony1-general] Inheritance and Replication Sets
- Next message: [Slony1-general] Can't build Slony-1.1.0.beta5 rpm as non-root user
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I'm about to start getting the slony-I 1.1 port ready for freebsd's package system. I have a concern about the upgrade process. In freebsd, the port system first removes the old package, then installs the new one when doing an upgrade. What will happen to the PG backend if a new one is forked during the window where there is no slony objects installed? I suspect it will fail to load the necessary objects... or is it already pre-loaded when the postmaster forks the child for the new connection? I'd like to be able to support an upgrade while the system continues to run, particularly on the origin servers. how does the RPM for redhat handle this? Vivek Khera, Ph.D. +1-301-869-4449 x806 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2476 bytes Desc: not available Url : http://gborg.postgresql.org/pipermail/slony1-general/attachments/20050524/cde4a317/smime-0001.bin
- Previous message: [Slony1-general] Inheritance and Replication Sets
- Next message: [Slony1-general] Can't build Slony-1.1.0.beta5 rpm as non-root user
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list