Skip site navigation (1) Skip section navigation (2)

Re: Failover of the Primary database and starting the standby database in Postgresql in PITR configuraiton?

From: "libra dba" <libra(dot)dba(at)gmail(dot)com>
To: salman <salmanb(at)quietcaresystems(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-20 16:49:18
Message-ID: 9abe84da0802200849w1f462558n270f4320a7465b6c@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-admin
thank you all!

On Feb 19, 2008 10:56 AM, salman <salmanb(at)quietcaresystems(dot)com> wrote:

>
>
> 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
>

In response to

Responses

pgsql-admin by date

Next:From: Darren ReedDate: 2008-02-20 19:14:44
Subject: Re: Power outage borked things (8.1.10)...
Previous:From: Tom LaneDate: 2008-02-20 16:10:28
Subject: Re: Power outage borked things (8.1.10)...

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group