Hi,
My main database server was not being replicated on standby server. In
standby's logs I am getting :
2011-06-16 16:22:03 IST FATAL: database system identifier differs
between the primary and standby
2011-06-16 16:22:03 IST DETAIL: The primary's identifier is
5618757375637716504, the standby's identifier is 5618757422882348667.
Does anybody have any idea ?
Regards,
Sanjay Rao
On 6/16/2011 2:50 PM, Sanjay Rao wrote:
Hi Rumman,
Can you send me link to "how to create postgres replication on windows."
I tried few hours as per following link, but not succeeded. Which
version of postgres are you using ? I tried using 9.0.
http://www.postgresql.org/docs/8.2/static/high-availability.html
Any type of help would be appreciated.
Regards,
Sanjay Rao
On 6/16/2011 2:01 PM, AI Rumman wrote:
Hi all,
I am a bit confused regarding streaming replication.
I have two server: A and B.
I set up replication successfully.
But when the master A goes down, B are not acting as master.
My recovery.conf as follows:
standby_mode = 'on'
primary_conninfo = 'host=10.0.0.91 port=5432 user=postgres'
trigger_file = 'C:\\pg\\stopreplication\\standby.txt'
restore_command = 'copy \pg\\wal_archive_91\\%f %p'
When I manually create the C:\\pg\\stopreplication\\standby.txt'
file, then it is working. That is, B is becoming the master.
So, my question is, how this trigger file should be created so that B
will become master automatically as soon as A goes down?
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
