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

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>
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 16:35:36
Message-ID: 4F33F5D8.3060207@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Jaime Casanova 2012-02-09 16:56:17 Re: pgsql: Have pg_receivexlog always send an invalid log position in statu
Previous Message Tom Lane 2012-02-09 15:17:59 Re: [COMMITTERS] pgsql: Add new keywords SNAPSHOT and TYPES to the keyword list in gram.