Message-ID: <508934FE.4020504@optionshouse.com>
Date: Thu, 25 Oct 2012 07:47:58 -0500
From: Shaun Thomas <sthomas@optionshouse.com>
Reply-To: <sthomas@optionshouse.com>
Organization: Peak6
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: Kevin Grittner <kgrittn@mail.com>
CC: Karl Denninger <karl@denninger.net>, Claudio Freire
	<klaussfreire@gmail.com>, delongboy <sdelong@saucontech.com>,
	<pgsql-performance@postgresql.org>
Subject: Re: How to upgrade from 9.1 to 9.2 with replication?
References: <20121025121003.306930@gmx.com>
In-Reply-To: <20121025121003.306930@gmx.com>
Content-Type: text/plain; charset="UTF-8"; format=flowed
content-transfer-encoding: 7bit

On 10/25/2012 07:10 AM, Kevin Grittner wrote:

> ... as long as the rsync was bracketed by calls to pg_start_backup()
> and pg_stop_backup().

Or they took it during a filesystem snapshot, or shut the database down.

I thought that the only thing start/stop backup did was mark the 
beginning and end transaction logs for the duration of the backup so 
they could be backed up separately for a minimal replay.

An rsync doesn't need that, because it's binary compatible. You get two 
exact copies of the database, provided data wasn't changing. That's easy 
enough to accomplish, really.

Or is there some embedded magic in streaming replication that requires 
start/stop backup? I've never had problems starting slaves built from an 
rsync before.


-- 
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604
312-444-8534
sthomas@optionshouse.com

______________________________________________

See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email