Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 65D01B5DBB7 for ; Tue, 7 Jun 2011 22:51:32 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 49366-05 for ; Wed, 8 Jun 2011 01:51:25 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-wy0-f174.google.com (mail-wy0-f174.google.com [74.125.82.174]) by mail.postgresql.org (Postfix) with ESMTP id 3A3E4B5D8B2 for ; Tue, 7 Jun 2011 22:51:25 -0300 (ADT) Received: by wya21 with SMTP id 21so22527wya.19 for ; Tue, 07 Jun 2011 18:51:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=Cmligt6U+N5uWUShBluoh8/pml/xaiKb4ui+dhPlMuQ=; b=irokyEKVdjYSDqrTfLIJvLvTu6ydCvzTJVkCZ5ARqFpuQKsgToveJ5Lk5J1oeJK6c9 8VXYF5wufQorTIkMHKLQIDg9CBbExshQ8qLoCTHyXcJufKuF0SPD5s7OrCKLVjGXOIwb 3rRGwq+OLVJczzuMitWv3LYjn64XBSizKoAr0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Sh1nYfXJLhIgBfv42LXm+Se7VblOkADBc4hm3ARq2FDorYEkoKIICx1zqMb2lKZgJb 1UKheQXQQKe1XqO1mbd8luf+1Lo/sbaYtwKM1REBlK855MjFJU4rvXiQk4bTL1MKbbch EPtmo2RwepZ8krp0qUMxZfZuXs7wQNm7VmHPw= MIME-Version: 1.0 Received: by 10.216.232.13 with SMTP id m13mr4327897weq.110.1307497885074; Tue, 07 Jun 2011 18:51:25 -0700 (PDT) Received: by 10.217.1.198 with HTTP; Tue, 7 Jun 2011 18:51:25 -0700 (PDT) In-Reply-To: <349220.32155.qm@web120008.mail.ne1.yahoo.com> 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> <349220.32155.qm@web120008.mail.ne1.yahoo.com> Date: Wed, 8 Jun 2011 10:51:25 +0900 Message-ID: Subject: Re: Switchover of Master and Slave roles From: Fujii Masao To: A J Cc: Kevin Grittner , Ray Stell , pgsql-admin@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.898 tagged_above=-10 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, RFC_ABUSE_POST=0.001 X-Spam-Level: X-Archive-Number: 201106/42 X-Sequence-Number: 37668 On Wed, Jun 8, 2011 at 3:59 AM, A J wrote: > 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. If the standby is completely sync with the master when failover happens, and if those two servers share the archive area, you can start new standby without taking a fresh base backup. You can do that by setting recovery_target_timeline to 'latest' in the recovery.conf and just starting new standby. Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center