Search Postgresql Archives

Re: upgrade to 8.2.? or implement Slony, which first?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



If you don't mind the downtime it would be simpler to upgrade to 8.2 and then worry about Slony. If you do mind you can use slony to do the upgrade which needs much less downtime as you switch servers.

Geoffrey wrote:
We plan to upgrade from our current 7.4.17 Postgresql to 8.2.? in the near future. We also plan to implement a replication solution, most likely Slony.

We know that the upgrade to 8.2.? will require some code changes.

Question is, is there a particular order in which we should perform these changes that would require the least amount of additional work?

That is, would it be more efficient to move to 8.2.? and then implement our Slony replication, or would there be less effort in implementing the Slony solution and then upgrading to 8.2.? ?


---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
      subscribe-nomail command to majordomo@xxxxxxxxxxxxxx so that your
      message can get through to the mailing list cleanly

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux