From: | salman <salmanb(at)quietcaresystems(dot)com> |
---|---|
To: | libra dba <libra(dot)dba(at)gmail(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Failover of the Primary database and starting the standby database in Postgresql in PITR configuraiton? |
Date: | 2008-02-19 15:56:55 |
Message-ID: | 47BAFC47.4060902@quietcaresystems.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
libra dba wrote:
> Hello all,
>
> Thanks for your response. The example shown by Charles Duffy, is quite
> impressive. Actually i built my replication based on this.
>
> But, i want to test the failover. In the example shown by Charles, mentions
> 'a trigger file' as it says:
> -------------------------------------------------------------------------------
> *touch ~/pg82demo/trigger*
> **
> *This should immediately cause the slave to finish processing archived
> segments, exit recovery mode, and come up ready for use.
> *
> -------------------------------------------------------------------------------
> what shold be the content of the trigger file. How do we cause the slave to
> finish the processing of the archived segments, exit the recovery mode and
> come up ready for use???
>
> Please help in the the FAILOVER of the primary and promoting the slave to
> the primary mode.
>
It's an empty file -- doesn't have to have anything in it. The script
simply checks to see if the file exists, and if it does, the recovery
loop is stopped.
-salman
From | Date | Subject | |
---|---|---|---|
Next Message | Douglas J Hunley | 2008-02-19 17:59:55 | why use -Ft or -Fc instead of the other on pg_dump? |
Previous Message | libra dba | 2008-02-19 14:23:20 | Re: Failover of the Primary database and starting the standby database in Postgresql in PITR configuraiton? |