Re: synchronous_commit = remote_flush

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: synchronous_commit = remote_flush
Date: 2016-08-18 20:25:49
Message-ID: CA+TgmoY2u45-vk4xQ3NuVtNor9ogVn6MjA0iUhhxT0uzu8GrUQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Aug 18, 2016 at 12:22 AM, Thomas Munro
<thomas(dot)munro(at)enterprisedb(dot)com> wrote:
> To do something about the confusion I keep seeing about what exactly
> "on" means, I've often wished we had "remote_flush". But it's not
> obvious how the backwards compatibility could work, ie how to keep the
> people happy who use "local" vs "on" to control syncrep, and also the
> people who use "off" vs "on" to control asynchronous commit on
> single-node systems. Is there any sensible way to do that, or is it
> not broken and I should pipe down, or is it just far too entrenched
> and never going to change?

I don't see why we can't add "remote_flush" as a synonym for "on". Do
you have something else in mind?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-08-18 20:30:52 Re: WIP: About CMake v2
Previous Message Christian Convey 2016-08-18 20:23:08 Re: WIP: About CMake v2