Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 7B1982E0041 for ; Tue, 19 Feb 2008 10:23:28 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 24232-02 for ; Tue, 19 Feb 2008 10:23:21 -0400 (AST) Received: from qb-out-0506.google.com (qb-out-0506.google.com [72.14.204.237]) by postgresql.org (Postfix) with ESMTP id 2FE682E003E for ; Tue, 19 Feb 2008 10:23:22 -0400 (AST) Received: by qb-out-0506.google.com with SMTP id o12so2100755qba.17 for ; Tue, 19 Feb 2008 06:23: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=MLR97SnFDAwzuckEN0NYKhx24+7yrd1aNyRbPoDEcns=; b=PQMKibrHOb41yWer6E3n8L64pPZWv73E1h4Hnn+RBxKqkaz1LmXfU8B4VrMu8e0GroClRis3Bq6Ci4wN1ZIT1ALUkdBobuRwB9Tkae+3+6AZ1RyCMzprcp6umY/Hwy8tmKIXg2LdW/4eZ9sOoVYgmYG8OdoAQGTlYHQk8Wm7LMc= 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=Icp8yO7lJ7XKtuydyw4aX6Y7abiZFMP2HfYFCyoi4pQSTyMeKJuVUuGpFollN6J+0zslOnhik1RF1zwF1MDetel9p7WGXZPoRWmshkaUqFyuvv5nCgxL24hYTXhIhYBJwVPSpu5dpLvWKX8NqnQ6zMWU76k4vevYZxbkBk0wlzA= Received: by 10.65.233.16 with SMTP id k16mr13498265qbr.43.1203431000435; Tue, 19 Feb 2008 06:23:20 -0800 (PST) Received: by 10.65.222.17 with HTTP; Tue, 19 Feb 2008 06:23:20 -0800 (PST) Message-ID: <9abe84da0802190623o2a24f2a5u9a44299fd634618e@mail.gmail.com> Date: Tue, 19 Feb 2008 09:23:20 -0500 From: "libra dba" To: "Simon Riggs" Subject: Re: Failover of the Primary database and starting the standby database in Postgresql in PITR configuraiton? Cc: "Praveen Kumar (TUV)" , pgsql-admin@postgresql.org In-Reply-To: <1203409158.16770.821.camel@ebony.site> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_10513_23386561.1203431000423" References: <84D57263D486374587DA0820E60A2CC601B07E23@srit_mail.renaissance-it.com> <1203409158.16770.821.camel@ebony.site> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200802/208 X-Sequence-Number: 28282 ------=_Part_10513_23386561.1203431000423 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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. Thanks! On Feb 19, 2008 3:19 AM, Simon Riggs wrote: > On Tue, 2008-02-19 at 09:53 +0530, Praveen Kumar (TUV) wrote: > > > Go through this below mentioned link > > > > > > > > http://archives.postgresql.org/sydpug/2006-10/msg00001.php > > I think people should be reading the manual, rather than reading an old > email. We have improved and corrected the manual, but old emails stay > the same. We can also change the manual some more in response to > clarifications. > > > -- > Simon Riggs > 2ndQuadrant http://www.2ndQuadrant.com > > ------=_Part_10513_23386561.1203431000423 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
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.
 
Thanks! 
On Feb 19, 2008 3:19 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
On Tue, 2008-02-19 at 09:53 +0530, Praveen Kumar (TUV) wrote:

> Go through this below mentioned link
>
>
>
> http://archives.postgresql.org/sydpug/2006-10/msg00001.php

I think people should be reading the manual, rather than reading an old
email. We have improved and corrected the manual, but old emails stay
the same. We can also change the manual some more in response to
clarifications.


--
 Simon Riggs
 2ndQuadrant  http://www.2ndQuadrant.com


------=_Part_10513_23386561.1203431000423--