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

Fujii Masao <masao.fujii@gmail.com>

From: Fujii Masao <masao.fujii@gmail.com>

To: Thom Brown <thom@linux.com>

Cc: Kevin Grittner <Kevin.Grittner@wicourts.gov>, Robert Haas <robertmhaas@gmail.com>, Jaime Casanova <jaime@2ndquadrant.com>, Simon Riggs <simon@2ndquadrant.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>

Date: 2012-04-17T19:29:12Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Add new replication mode synchronous_commit = 'write'.
- 443b4821f164 9.2.0 cited

Attachments

synchronous_commit_doc_v1.patch (application/octet-stream) patch v1

On Tue, Apr 17, 2012 at 9:52 PM, Thom Brown <thom@linux.com> wrote:
> On 16 April 2012 17:21, Fujii Masao <masao.fujii@gmail.com> wrote:
>> On Sun, Apr 15, 2012 at 12:13 AM, Thom Brown <thom@linux.com> wrote:
>>> No, that's not what I was referring to.  If you don't have a standby
>>> (i.e. a single, isolated database cluster with no replication), and
>>> its synchronous_commit is set to 'remote_write', what effect does that
>>> have?
>>
>> It's the same effect as 'on' and 'local' do, i.e., transaction commit waits
>> for only local WAL flush. This behavior is not documented explicitly...
>> How should we change the document? What about adding the following
>> into the explanation of synchronous_commit parameter (maybe the end
>> of second paragraph of that)?
>>
>> -----------------
>> If synchronous_standby_names is not set, on, remote_write and local
>> provide the same synchronization level; transaction commit only waits for
>> local flush.
>> -----------------
>
> Yes, that sounds fine.

Okay, patch attached.

Regards,

-- 
Fujii Masao