Re: WIP partial replication patch

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Boszormenyi Zoltan <zb(at)cybertec(dot)at>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Hans-Juergen Schoenig <hs(at)cybertec(dot)at>
Subject: Re: WIP partial replication patch
Date: 2010-08-14 13:21:42
Message-ID: 7228.1281792102@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)anarazel(dot)de> writes:
> On Sat, Aug 14, 2010 at 08:40:24AM +0200, Boszormenyi Zoltan wrote:
>> And in this patch, the startup process only tries to connect
>> after signalling the postmaster that a consistent state is reached.
>> And the connection has a reasonable timeout built in.

> I don't think you currently can guarantee you allways have enough
> local WAL to even reach a consistent point.

Even if you do, the patch will malfunction (and perhaps corrupt the
database) while reading that WAL. Yes, it'd work once you reach a
consistent database state, but bootstrapping a slave into that
condition will be far more painful than it is with the current
replication code.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-08-14 13:23:33 Re: Re: [COMMITTERS] pgsql: Recognize functional dependency on primary keys.
Previous Message Bruce Momjian 2010-08-14 13:02:22 Re: Re: [COMMITTERS] pgsql: Recognize functional dependency on primary keys.