From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Hannu Krosing <hannu(at)krosing(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, Markus Wanner <markus(at)bluegap(dot)ch>, ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Synchronous Log Shipping Replication |
Date: | 2008-09-15 13:09:35 |
Message-ID: | 20080915130935.GB3798@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Simon Riggs escribió:
> On Fri, 2008-09-12 at 17:08 +0300, Heikki Linnakangas wrote:
> > > It should be clear that to make this work you must run with a base
> > > backup that was derived correctly on the current master. You can do that
> > > by re-copying everything, or you can do that by just shipping changed
> > > blocks (rsync etc). So I don't see a problem in the first place.
> >
> > Hmm, built-in rsync capability would be cool. Probably not in the first
> > phase, though..
>
> Built-in? Why? I mean make base backup using rsync. That way only
> changed data blocks need be migrated, so much faster.
Why rsync? Just compare the LSNs ...
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Brendan Jurd | 2008-09-15 13:15:54 | Re: Parsing of pg_hba.conf and authentication inconsistencies |
Previous Message | Merlin Moncure | 2008-09-15 13:07:12 | Re: Transaction Snapshots and Hot Standby |