Re: pgsql: Have pg_receivexlog always send an invalid log position in statu - Mailing list pgsql-committers

From Magnus Hagander
Subject Re: pgsql: Have pg_receivexlog always send an invalid log position in statu
Date
Msg-id CABUevEyB3x_wC6mmBXHSbuYdyNQRJHnkWSbrBDg7eddcBmzPBw@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Have pg_receivexlog always send an invalid log position in statu  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: pgsql: Have pg_receivexlog always send an invalid log position in statu
List pgsql-committers
On Thu, Feb 9, 2012 at 17:35, Heikki Linnakangas
<heikki.linnakangas@enterprisedb.com> wrote:
> On 09.02.2012 15:14, Magnus Hagander wrote:
>>
>> Have pg_receivexlog always send an invalid log position in status messages
>>
>> This prevents pg_basebackup and pg_receivexlog from becoming a synchronous
>> standby in case 'write' is used for synchronous_commit.
>
>
> It's not completely crazy to use pg_receivexlog as a synchronous standby. It
> provides the zero-loss property like a real standby does, ie. if the master
> dies after sending the WAL to pg_receivexlog, that transaction is safe in
> the archive.

Yes, but as I stated in the email in the thread that the patch was
posted in, I think this should not be the default behaviour, but it
should be available as a commandline option, or something along that
line.

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

pgsql-committers by date:

Previous
From: Peter Eisentraut
Date:
Subject: pgsql: psql: Support zero byte field and record separators
Next
From: Fujii Masao
Date:
Subject: Re: pgsql: Have pg_receivexlog always send an invalid log position in statu