| From: | Shaun Thomas <sthomas(at)optionshouse(dot)com> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)mail(dot)com> |
| Cc: | Karl Denninger <karl(at)denninger(dot)net>, Claudio Freire <klaussfreire(at)gmail(dot)com>, delongboy <sdelong(at)saucontech(dot)com>, <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: How to upgrade from 9.1 to 9.2 with replication? |
| Date: | 2012-10-25 12:47:58 |
| Message-ID: | 508934FE.4020504@optionshouse.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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(at)optionshouse(dot)com
______________________________________________
See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email
| From | Date | Subject | |
|---|---|---|---|
| Next Message | delongboy | 2012-10-25 14:12:04 | Re: How to upgrade from 9.1 to 9.2 with replication? |
| Previous Message | Kevin Grittner | 2012-10-25 12:10:03 | Re: How to upgrade from 9.1 to 9.2 with replication? |