Re: Causal reads take II

From: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
To: Dmitry Dolgov <9erthalion6(at)gmail(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Causal reads take II
Date: 2017-06-29 12:55:15
Message-ID: CAEepm=0YigNQczAF-=x_SxT6cJv77Yb0EO+cAFnqRyVu4+bKFw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-hackers

On Sat, Jun 24, 2017 at 4:05 PM, Thomas Munro
<thomas(dot)munro(at)enterprisedb(dot)com> wrote:
> On Fri, Jun 23, 2017 at 11:48 PM, Thomas Munro
> <thomas(dot)munro(at)enterprisedb(dot)com> wrote:
>> Maybe it needs a better name.
>
> Ok, how about this: the feature could be called "synchronous replay".
> The new column in pg_stat_replication could be called sync_replay
> (like the other sync_XXX columns). The GUCs could be called
> synchronous replay, synchronous_replay_max_lag and
> synchronous_replay_lease_time. The language in log messages could
> refer to standbys "joining the synchronous replay set".

Feature hereby renamed that way. It seems a lot more
self-explanatory. Please see attached.

--
Thomas Munro
http://www.enterprisedb.com

Attachment Content-Type Size
synchronous-replay-v1.patch application/octet-stream 76.6 KB
test-synchronous-replay.sh application/x-sh 1.9 KB
test-synchronous-replay.c text/x-csrc 5.5 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Merlin Moncure 2017-06-29 13:08:51 Re: [HACKERS] Segmentation fault in libpq
Previous Message Robert Haas 2017-06-29 12:18:17 Re: protocol version negotiation (Re: Libpq PGRES_COPY_BOTH - version compatibility)