Re: synchronous_commit = remote_flush - Mailing list pgsql-hackers

From Christoph Berg
Subject Re: synchronous_commit = remote_flush
Date
Msg-id 20160821121630.vz6pvnkbokpemfk5@msg.df7cb.de
Whole thread Raw
In response to Re: synchronous_commit = remote_flush  (Thomas Munro <thomas.munro@enterprisedb.com>)
List pgsql-hackers
Re: Thomas Munro 2016-08-21 <CAEepm=0EQvwhFih7wZ+cHL=UJDvF4KSe0thw1gPEY-ga3DcvmQ@mail.gmail.com>
> Right, we could just add it to guc.c after "on", so that you can "SET
> synchronous_commit TO remote_flush", but then "SHOW
> synchronous_commit" returns "on".
> 
> The problem I was thinking about was this: if you add "remote_flush"
> before "on" in guc.c, then "SHOW ..." will return "remote_flush",
> which would be really helpful for users trying to understand what
> syncrep is actually doing; but it would probably confuse single node
> users and async replication users.

Maybe "flush" would work, given it applies locally and on the remote
side? (And "local" could be "local_flush"...?)

Christoph



pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: synchronous_commit = remote_flush
Next
From: Emre Hasegeli
Date:
Subject: Re: [PATCH] Alter or rename enum value