Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 95C052E00F9 for ; Wed, 20 Feb 2008 12:51:38 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 11142-04 for ; Wed, 20 Feb 2008 12:51:34 -0400 (AST) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.180]) by postgresql.org (Postfix) with ESMTP id 096522E0187 for ; Wed, 20 Feb 2008 12:49:20 -0400 (AST) Received: by py-out-1112.google.com with SMTP id d37so4562999pye.29 for ; Wed, 20 Feb 2008 08:49:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=LLjQ/0I9P5/yWLlwvykbXLgu0wkVYnc47wlREkIpZIY=; b=tjkFaCkoXIUFIxUP0zS1gqZkcjTGu1ilJJAdptkdQ5r5oKcgP27qJNWDu5c3LKOjlRZV+N5ViP2xtotaV7m5JP3i8IChkbyWvKxyNsa1u8KOricVSTNqoAesy08vbqo0MJjQ05eSs50nLGOx/6FeAmUu7sZ4gPrjme5+Xr2ldQE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=it1e4Jntx1fIuz4Bqnf479AnINpXKm+ohMar67tyrThuffnJaewmk6yG71O0WAsoftHDaToV0tLx3Kd537ypLbJJyIY+mNtbDXFFWNV2cn6t4YTFIzjYK9IspvMTC3ptqJQG8iE/2AXmlynMIZEnQdeWZoN/+1QGtgQ7Hqvsb04= Received: by 10.65.220.8 with SMTP id x8mr16883757qbq.24.1203526158745; Wed, 20 Feb 2008 08:49:18 -0800 (PST) Received: by 10.65.222.17 with HTTP; Wed, 20 Feb 2008 08:49:18 -0800 (PST) Message-ID: <9abe84da0802200849w1f462558n270f4320a7465b6c@mail.gmail.com> Date: Wed, 20 Feb 2008 11:49:18 -0500 From: "libra dba" To: salman Subject: Re: Failover of the Primary database and starting the standby database in Postgresql in PITR configuraiton? Cc: pgsql-admin@postgresql.org In-Reply-To: <47BAFC47.4060902@quietcaresystems.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_16107_5019917.1203526158706" References: <84D57263D486374587DA0820E60A2CC601B07E23@srit_mail.renaissance-it.com> <1203409158.16770.821.camel@ebony.site> <9abe84da0802190623o2a24f2a5u9a44299fd634618e@mail.gmail.com> <47BAFC47.4060902@quietcaresystems.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/238 X-Sequence-Number: 28312 ------=_Part_16107_5019917.1203526158706 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline thank you all! On Feb 19, 2008 10:56 AM, salman 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 > ------=_Part_16107_5019917.1203526158706 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline thank you all!

On Feb 19, 2008 10:56 AM, salman <salmanb@quietcaresystems.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

------=_Part_16107_5019917.1203526158706--