Skip site navigation (1) Skip section navigation (2)

Re: [COMMITTERS] pgsql: Add new replication mode synchronous_commit = 'write'.

From: Thom Brown <thom(at)linux(dot)com>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Jaime Casanova <jaime(at)2ndquadrant(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Add new replication mode synchronous_commit = 'write'.
Date: 2012-04-13 19:16:28
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-committerspgsql-hackers
On 13 April 2012 19:15, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> In my view, remote_write seems a lot more clear than write
> +1
> I sure didn't understand it to mean remote_write when I read the
> subject line.

Whatever this option value is named, it needs to be referenced in the
postgresql.conf comment for this option, as it isn't currently.

I have a question though.  What happens when this is set to "write"
(or "remote_write" as proposed) but it's being used on a standalone
primary?  At the moment it's not documented what level of guarantee
this would provide.


In response to


pgsql-hackers by date

Next:From: Heikki LinnakangasDate: 2012-04-13 19:21:48
Subject: Re: PREPARE TRANSACTION compatibility?
Previous:From: Robert HaasDate: 2012-04-13 19:15:28
Subject: Re: Patch: add timing of buffer I/O requests

pgsql-committers by date

Next:From: Guillaume LelargeDate: 2012-04-13 19:57:58
Subject: Re: [COMMITTERS] pgsql: Add new replication mode synchronous_commit = 'write'.
Previous:From: Peter EisentrautDate: 2012-04-13 18:39:16
Subject: pgsql: Rename bytea_agg to string_agg and add delimiter argument

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group