Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 00512B5DF4D for ; Tue, 7 Jun 2011 15:59:34 -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 31411-04 for ; Tue, 7 Jun 2011 18:59:26 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from nm19.bullet.mail.ne1.yahoo.com (nm19.bullet.mail.ne1.yahoo.com [98.138.90.82]) by mail.postgresql.org (Postfix) with SMTP id 8E45FB5DF46 for ; Tue, 7 Jun 2011 15:59:26 -0300 (ADT) Received: from [98.138.90.56] by nm19.bullet.mail.ne1.yahoo.com with NNFMP; 07 Jun 2011 18:59:25 -0000 Received: from [98.138.87.5] by tm9.bullet.mail.ne1.yahoo.com with NNFMP; 07 Jun 2011 18:59:25 -0000 Received: from [127.0.0.1] by omp1005.mail.ne1.yahoo.com with NNFMP; 07 Jun 2011 18:59:07 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 475982.52241.bm@omp1005.mail.ne1.yahoo.com Received: (qmail 3730 invoked by uid 60001); 7 Jun 2011 18:59:07 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1307473147; bh=1xJxLJY8HqsZZKNTLa60pIJvBuILUeAPn9SqIyjHgj4=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=THBhtO5pmPgea+pDN4p4LL8ESckcOYMMuvChR5ICCWG6xsXoAhcPRYkGxUbXnJny4rpsbPRTdiPDX1XrEJgpkT7EoR2Eia38UWZ9ljt5Eum+hEaLVDd97ymw1y+/lhzWd5ql+I3rJFd/1IViv5JVw3Qe0961pFNvrIpL6YXMZKc= 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=xgCvPdp7K9ndkOK1x48+GLGOrl0rbPIs0cIDZ26JqVRiBgcSfS5pyLaem05w7x419RS+zBUCfJN1+2eoSl8qJcHZhiaiRlKHVIBwHxboqH8n9kwrfzM69xauHcqp6c5wFlLB2Yl5LnybiKSc+l3X9lZF+ZFF7IdZzXf0NZ2ycIM=; Message-ID: <349220.32155.qm@web120008.mail.ne1.yahoo.com> X-YMail-OSG: 5h5YIJAVM1lmgh0mPDuN8JlXxs...EQUM0GmDdT27TxarDD ayYibTqQmaQmKMckBTH4SvclEbG9aRq_0HrcZnkNqKSRAhvFfAdbtvBHM0Zh YbWNMdpbLg1Im5mdgtN_KHe4_cwh3mGoiqgHxxzsNTLbfcuKsslVR7pCwNdi bZAUgHNAu.qG2a5FO6BDM0Xm1FFXe01OihNzuC41.V5CEYaPu_EKJg1Uk8DQ KZaqYlDOEFPik1TgSy6l64TRDnYS7S1J80Rbx9zFsCWIjjIj36zc.ECyCovB 5SLzIikHT_MTv4zabs3qckxFB5XlOjoRERXlUXNkvdVVhomU- Received: from [64.61.91.74] by web120008.mail.ne1.yahoo.com via HTTP; Tue, 07 Jun 2011 11:59:07 PDT X-Mailer: YahooMailRC/570 YahooMailWebService/0.8.111.304355 References: <693391.31715.qm@web120020.mail.ne1.yahoo.com> <20110607181244.GA3861@cns.vt.edu> <264025.13168.qm@web120005.mail.ne1.yahoo.com> <4DEE2B49020000250003E2A2@gw.wicourts.gov> Date: Tue, 7 Jun 2011 11:59:07 -0700 (PDT) From: A J Subject: Re: Switchover of Master and Slave roles To: Kevin Grittner , Ray Stell Cc: pgsql-admin@postgresql.org In-Reply-To: <4DEE2B49020000250003E2A2@gw.wicourts.gov> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-314295098-1307473147=:32155" 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/35 X-Sequence-Number: 37661 --0-314295098-1307473147=:32155 Content-Type: text/plain; charset=us-ascii Ok. So if I understand it correctly, as far as Postgres is concerned the 'mirror is broken'. It is a one-time cutover. We then rely on filesystem tools (or other third party tools) to get the original master in sync with the new master efficiently and then make it join as slave. Right ? ________________________________ From: Kevin Grittner To: Ray Stell ; A J Cc: pgsql-admin@postgresql.org Sent: Tue, June 7, 2011 2:44:41 PM Subject: Re: [ADMIN] Switchover of Master and Slave roles A J wrote: > 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 ? The old server will probably be close enough that judicious use of rsync with the old copy as the target will allow a base backup to be taken very quickly. -Kevin --0-314295098-1307473147=:32155 Content-Type: text/html; charset=us-ascii
Ok. So if I understand it correctly, as far as Postgres is concerned the 'mirror is broken'. It is a one-time cutover.
We then rely on filesystem tools (or other third party tools) to get the original master in sync with the new master efficiently and then make it join as slave.
Right ?


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

A J <s5aly@yahoo.com> wrote:

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

The old server will probably be close enough that judicious use of
rsync with the old copy as the target will allow a base backup to be
taken very quickly.

-Kevin
--0-314295098-1307473147=:32155--