Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 7F057B5DC29 for ; Tue, 7 Jun 2011 15:34:15 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 91584-09 for ; Tue, 7 Jun 2011 18:34:07 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from nm20-vm2.bullet.mail.ne1.yahoo.com (nm20-vm2.bullet.mail.ne1.yahoo.com [98.138.91.208]) by mail.postgresql.org (Postfix) with SMTP id 2F663B5DC19 for ; Tue, 7 Jun 2011 15:34:06 -0300 (ADT) Received: from [98.138.90.48] by nm20.bullet.mail.ne1.yahoo.com with NNFMP; 07 Jun 2011 18:34:06 -0000 Received: from [98.138.89.164] by tm1.bullet.mail.ne1.yahoo.com with NNFMP; 07 Jun 2011 18:34:06 -0000 Received: from [127.0.0.1] by omp1020.mail.ne1.yahoo.com with NNFMP; 07 Jun 2011 18:33:56 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 371200.53808.bm@omp1020.mail.ne1.yahoo.com Received: (qmail 20523 invoked by uid 60001); 7 Jun 2011 18:33:56 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1307471636; bh=zQ9eJN/Du0Y17MR0DNmpg9RmKjvd07/axhgSVBljaOQ=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=PqXqa6XAMOEXE1NIdTxYcqh/Vm6qqzQLzTRqzYXhY1p7iMpU/OvlTeUiTFFfLxU0aWWbaLHm7sStSXA00VveTrwTNt7p6kRKE4qtJmfye4dbREuEzkDD01OF/Qz5rBa69far5ZlJZQQOd7Dosk3+/NF2C8L5lU+Fe+yacQgyLzQ= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=NgX453cJf+I7BCUZ5YpgyqBUGwdyyvXGum2iFT4n8Awyv+29Aq7sPjsWKOAkV1HyTp/lgWCChjVr36M21KQnV3xcBMbZFHTUAiaWsZOZySG8MIO00Dj2VgIzvbvb8Jukg5niAXgo1V5s89ws/4l2rhhjB/oFrTPIAUj6mpIWBsA=; Message-ID: <264025.13168.qm@web120005.mail.ne1.yahoo.com> X-YMail-OSG: 05eo7QQVM1k3.u8ZZFifbLGC9zJgEvUeVCLSsbz7L6PnQ_F .ps2vl0.KeO7c81xVPQ1i3HwaKKa02y9G1EwFYxqOvLSM1ehp8Go9zmQB8Wn 7p2kPePiZK4Ze8m4K_bPjwBit1U30YCeH8.QAtGITJ7IiLzPZF._6.opmEbh a5HnJ8_YlLKtWjZYqA86SPHAaelOwCdjLMcgJ4zFTPhThAz8gW9prOZ25Bq8 ErUFEwfZSP_MX0SxuIST5N_1FhUdLpdMq1Qpuwv6y89YKiDGz4RO2dGVyDWe eDNPwRYxI9.J6v7W6XcBR2KwLUgOe.osBI9qKY1whhWsSdct11aIAMP5bbRD rmKPyVtRu Received: from [64.61.91.74] by web120005.mail.ne1.yahoo.com via HTTP; Tue, 07 Jun 2011 11:33:56 PDT X-Mailer: YahooMailRC/570 YahooMailWebService/0.8.111.304355 References: <693391.31715.qm@web120020.mail.ne1.yahoo.com> <20110607181244.GA3861@cns.vt.edu> Date: Tue, 7 Jun 2011 11:33:56 -0700 (PDT) From: A J Subject: Re: Switchover of Master and Slave roles To: Ray Stell Cc: pgsql-admin@postgresql.org In-Reply-To: <20110607181244.GA3861@cns.vt.edu> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1544563754-1307471636=:13168" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.907 tagged_above=-10 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RFC_ABUSE_POST=0.001, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201106/32 X-Sequence-Number: 37658 --0-1544563754-1307471636=:13168 Content-Type: text/plain; charset=us-ascii >>To return to normal operation, a standby server must be recreated, either on the >>former primary system when it comes up<< What does it exactly mean to 'recreate a standby server' ? Can I not use the datafiles on the former primary and just let it sync and get the incremental from the new primary ? Do I have to remove all the data files from the former primary and get all the datafiles through rsync (or other similar manner) from the new primary ? ________________________________ From: Ray Stell To: A J Cc: pgsql-admin@postgresql.org Sent: Tue, June 7, 2011 2:12:44 PM Subject: Re: [ADMIN] Switchover of Master and Slave roles On Tue, Jun 07, 2011 at 09:32:31AM -0700, A J wrote: > Hello, > I am trying to switch the master and slave roles in a test I am doing with > streaming replication in 9.1 beta. > http://www.postgresql.org/docs/9.1/static/warm-standby-failover.html Once failover to the standby occurs, there is only a single server in operation. This is known as a degenerate state. The former standby is now the primary, but the former primary is down and might stay down. To return to normal operation, a standby server must be recreated, either on the former primary system when it comes up, or on a third, possibly new, system. Once complete, the primary and standby can be considered to have switched roles. --0-1544563754-1307471636=:13168 Content-Type: text/html; charset=us-ascii
>>To return to normal operation, a standby server must be recreated, either on the former primary system when it comes up<<

What does it exactly mean to 'recreate a standby server' ? Can I not use the datafiles on the former primary and just let it sync and get the incremental from the new primary ? Do I have to remove all the data files from the former primary and get all the datafiles through rsync (or other similar manner) from the new primary ?


From: Ray Stell <stellr@cns.vt.edu>
To: A J <s5aly@yahoo.com>
Cc: pgsql-admin@postgresql.org
Sent: Tue, June 7, 2011 2:12:44 PM
Subject: Re: [ADMIN] Switchover of Master and Slave roles

On Tue, Jun 07, 2011 at 09:32:31AM -0700, A J wrote:
> Hello,
> I am trying to switch the master and slave roles in a test I am doing with
> streaming replication in 9.1 beta.
>

http://www.postgresql.org/docs/9.1/static/warm-standby-failover.html

Once failover to the standby occurs, there is only a single server in
operation. This is known as a degenerate state. The former standby is
now the primary, but the former primary is down and might stay down. To
return to normal operation, a standby server must be recreated, either
on the former primary system when it comes up, or on a third, possibly
new, system. Once complete, the primary and standby can be considered
to have switched roles.
--0-1544563754-1307471636=:13168--