Re: Synchronous Log Shipping Replication

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Simon Riggs <simon(at)2ndQuadrant(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:20:02
Message-ID: 48CE6102.8070508@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera wrote:
> 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 ...

True, that's much better. Only works for data files, though, so we'll
still need something else for clog etc. But the volume of the other
stuff is much smaller, so I support we don't need to bother delta
compressing them.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2008-09-15 13:24:23 Re: rmgr hooks and contrib/rmgr_hook
Previous Message Brendan Jurd 2008-09-15 13:15:54 Re: Parsing of pg_hba.conf and authentication inconsistencies