From: Shaun Thomas <sthomas@optionshouse.com>
To: Kevin Grittner <kgrittn@mail.com>
Cc: Karl Denninger <karl@denninger.net>
Cc: Claudio Freire <klaussfreire@gmail.com>
Cc: delongboy <sdelong@saucontech.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: How to upgrade from 9.1 to 9.2 with replication?
Date: Thu, 25 Oct 2012 07:47:58 -0500
Message-ID: <508934FE.4020504@optionshouse.com> (raw)
In-Reply-To: <20121025121003.306930@gmx.com>
References: <20121025121003.306930@gmx.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: sthomas@optionshouse.com, kgrittn@mail.com, karl@denninger.net, klaussfreire@gmail.com, sdelong@saucontech.com
Subject: Re: How to upgrade from 9.1 to 9.2 with replication?
In-Reply-To: <508934FE.4020504@optionshouse.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox