I wonder how to quickly recovery failed master? If I directly startup the
failed master as slave ( assign proper parameter), is there any problem? For
example, I don't do any copy operation in script of
recovery_1st_stage_command and recovery_2st_stage_command.
According to this document:
On Tue, Mar 4, 2014 at 6:26 PM, leo dazhou...@gmail.com wrote:
I wonder how to quickly recovery failed master? If I directly startup the
failed master as slave ( assign proper parameter), is there any problem?
Yep, if the master has got ahead of the slave in term of WAL replay
where WAL forked
I find a solution to short the recover time by configure parameter
Synchronous Transfer. Refer to :
https://wiki.postgresql.org/wiki/Synchronous_Transfer.
But I don't which postgreSQL will enable this parameter, I install
9.3.3-1 on redhat, but I don't find this parameter in postgresql.conf.
On Wed, Mar 5, 2014 at 2:14 PM, leo dazhou...@gmail.com wrote:
I find a solution to short the recover time by configure parameter
Synchronous Transfer. Refer to :
https://wiki.postgresql.org/wiki/Synchronous_Transfer.
But I don't which postgreSQL will enable this parameter, I install
Hi,
I am evaluating the HA solution of PostgreSQL 9.3.
1. Pacemaker resource agent for PostgreSQL + PostgreSQL sync stream
replication
2. PG-Pool + PostgreSQL sync stream replication
According to my understanding, above two solution must be done same
things to recovery
I am evaluating the HA solution of PostgreSQL 9.3.
1. Pacemaker resource agent for PostgreSQL + PostgreSQL sync stream
replication
2. PG-Pool + PostgreSQL sync stream replication
According to my understanding, above two solution must be done same
things to recovery
