I am planning to upgrade my Postgres DB server from v8.4 to a newer version.
Should 9.2 be a good choice for upgrading, it has the best features around
replication. Also can someone help me with a guide for the upgrade process
and rollback process in case anything fails.
Thanks,
Rajiv
Yes, PostgreSQL 9.2 would be an excellent choice; There are various upgrade
options available like dump/restore, slony and pg_upgrade where each have
their pros and cons. The selection of upgrade method solely depend upon the
data size and available downtime. It's strongly recommended to test
I recently upgraded from the 8.2 branch to 9.2. Since mine was so old the
only option I had was the dump/restore functionality, but that's really a
simple procedure, just potentially time consuming based on your data and
computers. It's also good to look over the release notes between the
Hi,
I am using Postgres DB with stand by database, configured with streaming in
synchronized mode (each commit on primary DB waits for commit on secondary DB).
Sometimes we suffer from network issues and as consequences, secondary machine
is not available.
In these situations, our
On Apr 18, 2013, at 9:40 AM, Sofer, Yuval wrote:
Is there any parameter that I can use, to enable recovering from hanging on
until someone of us re-establish connection to secondary DB?
Maybe some configuration parameter that sets the time interval for being
stuck because of unavailable
Hell**o Yuval,
I would suggest to buy a third server if you want to do synchronous
replication.
However, if your network is broken, I would first fix the network. :)
cheers,
Bert
On Thu, Apr 18, 2013 at 6:13 PM, Scott Ribe scott_r...@elevated-dev.comwrote:
On Apr 18, 2013, at 9:40 AM,
