Any takers on this issue?
---------- Forwarded message ----------
From: Selva manickaraja <mavles78(at)gmail(dot)com>
Date: Sun, Feb 20, 2011 at 3:24 PM
Subject: Standby function after fail-over
We are in the midst of setting up fail-over arrangements between a primary
In the primary we have set the "archive_command" to copy the WAL(s) to a
shared directory "archive_dir" accessible by both Primary and Secondary.
As the Secondary is meant to fail-over. The "restore_command" will recover
the WAL(s) from "archive_dir". Once it becomes the Primary, can it assume
the role of the initial Primary to copy the WAL(s) to "archive_dir". This
means the "archive_command" and "archive_mode" settings need to be as same
as the initial Primary. One thing to note here is that the "hot_standby" has
been to "on" in the Secondary to function as a read-only server. What is
expected to happen if the Secondary fails-over? Can it copy the WAL(s) to
"archive_dir" just as the Primary did? Or must be change the setting after
the fail-over and initiate a restart?
In response to
pgsql-admin by date
|Next:||From: Selva manickaraja||Date: 2011-02-21 01:04:43|
|Subject: Re: Trigger File Behaviour|
|Previous:||From: Greg Smith||Date: 2011-02-20 16:52:57|
|Subject: Re: Corrupted disk|