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

From Heikki Linnakangas
Subject Re: pgsql: Have pg_receivexlog always send an invalid log position in statu
Date
Msg-id 4F33F5D8.3060207@enterprisedb.com
Whole thread Raw
In response to pgsql: Have pg_receivexlog always send an invalid log position in statu  (Magnus Hagander <magnus@hagander.net>)
Responses Re: pgsql: Have pg_receivexlog always send an invalid log position in statu  (Jaime Casanova <jaime@2ndquadrant.com>)
Re: pgsql: Have pg_receivexlog always send an invalid log position in statu  (Magnus Hagander <magnus@hagander.net>)
List pgsql-committers
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.

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

pgsql-committers by date:

Previous
From: Magnus Hagander
Date:
Subject: pgsql: Have pg_receivexlog always send an invalid log position in statu
Next
From: Jaime Casanova
Date:
Subject: Re: pgsql: Have pg_receivexlog always send an invalid log position in statu