From: Michael Paquier <michael@paquier.xyz>
To: Maksim Milyutin <milyutinma@gmail.com>
Cc: Thomas Munro <thomas.munro@enterprisedb.com>
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: Typo in description of replay_lag attribute in pg_stat_replication view
Date: Wed, 5 Dec 2018 10:04:55 +0900
Message-ID: <20181205010455.GA2407@paquier.xyz> (raw)
In-Reply-To: <0cfde408-a360-3461-124c-cfa0c72e3b0d@gmail.com>
References: <27b3b80c-3615-2d76-02c5-44566b53136c@gmail.com>
<20181204001802.GK3423@paquier.xyz>
<CAEepm=3rVm=krEhefk-o=e4KTG3ry_QMJWcn7DgFSGbOc4_UYQ@mail.gmail.com>
<20181204021925.GM3423@paquier.xyz>
<0cfde408-a360-3461-124c-cfa0c72e3b0d@gmail.com>
On Wed, Dec 05, 2018 at 01:24:22AM +0300, Maksim Milyutin wrote:
> Yeah, I think the notion *remote_flush level* is more appropriate especially
> in the context of sync replication. Within this context maybe it makes sense
> to replace the word *level* to *value* in description of *flush_lag*?
I am not sure that this is an improvement. Anyway, I have committed
your original patch as that's clearly a mistake and back-patched down to
v10.
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: michael@paquier.xyz, milyutinma@gmail.com, thomas.munro@enterprisedb.com, pgsql-docs@lists.postgresql.org
Subject: Re: Typo in description of replay_lag attribute in pg_stat_replication view
In-Reply-To: <20181205010455.GA2407@paquier.xyz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox