Re: pgsql: Have pg_receivexlog always send an invalid log position in statu

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Have pg_receivexlog always send an invalid log position in statu
Date: 2012-02-09 23:14:41
Message-ID: CABUevEyB3x_wC6mmBXHSbuYdyNQRJHnkWSbrBDg7eddcBmzPBw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Thu, Feb 9, 2012 at 17:35, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)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/

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Fujii Masao 2012-02-10 03:34:44 Re: pgsql: Have pg_receivexlog always send an invalid log position in statu
Previous Message Tom Lane 2012-02-09 18:30:27 Re: [COMMITTERS] pgsql: Add new keywords SNAPSHOT and TYPES to the keyword list in gram.