hi, i tried the exact setup that you described here, but unfortunately i had to
restart the new master(former slave) in order to get the new settings and this
will conduct to a downtime and service interruption.
anyway thanks for sharing your experience.
Adrian Videanu
--- On Fri, 4/20/12, jen
hi
we did a new shell script named recovery_config_chage.sh at standby server.
the script I wanted to change the fail down postgres master config ,let it
start as standby server
and build the communication with the former standby now is master server,then
started it by remotestart.sh
the abo
so, just to make sure that i understand:
after the master failed, the slave become the new master, the you have changed
postgresql.conf from master to slave and viceversa and restarted the old master
as slave ?
--- On Thu, 4/19/12, jenopob [via PostgreSQL]
wrote:
From: jenopob [via PostgreSQ
Hi there,
i have the exact same problem. Did you find a solution for this ?
thanks,
Adrian Videanu
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/How-to-auto-swtich-the-roles-of-primary-and-standby-tp4546630p5645680.html
Sent from the PostgreSQL - admin mailing list arc
hi all
my architecture follows as:
Master/Slave with Streaming Replication and pgpool-II
version of pgpool-II is pgpool-II.3.0.4
version of PostgreSQL is 9.0.2
http://postgresql.1045698.n5.nabble.com/file/n4546630/pgpool-II.png
I want to confirm some questions as follows:
1.how about the perfor
