From: Fujii Masao <masao.fujii@oss.nttdata.com>
To: Michael Paquier <michael@paquier.xyz>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Postgres hackers <pgsql-hackers@lists.postgresql.org>
Cc: Thomas Munro <thomas.munro@gmail.com>
Subject: Re: pg_stat_wal_receiver and flushedUpto/writtenUpto
Date: Tue, 19 May 2020 23:38:52 +0900
Message-ID: <c049ffcf-d2fe-90f7-c8ba-0741035aa6a7@oss.nttdata.com> (raw)
In-Reply-To: <20200517010857.GI212736@paquier.xyz>
References: <20200515230539.GC212736@paquier.xyz>
<20200515233446.GA334@alvherre.pgsql>
<20200516011547.GD212736@paquier.xyz>
<20200517010857.GI212736@paquier.xyz>
On 2020/05/17 10:08, Michael Paquier wrote:
> On Sat, May 16, 2020 at 10:15:47AM +0900, Michael Paquier wrote:
>> Thanks. If there are no objections, I'll revisit that tomorrow and
>> apply it with those changes, just in time for beta1.
>
> Okay, done this part then.
I found that "received_lsn" is still used in high-availability.sgml.
We should apply the following change in high-availability?
- view's <literal>received_lsn</literal> indicates that WAL is being
+ view's <literal>flushed_lsn</literal> indicates that WAL is being
BTW, we have pg_last_wal_receive_lsn() that returns the same lsn as
pg_stat_wal_receiver.flushed_lsn. Previously both used the term "receive"
in their names, but currently not. IMO it's better to use the same term in
those names for the consistency, but it's not good idea to rename
pg_last_wal_receive_lsn() to something like pg_last_wal_receive_lsn().
I have no better idea for now. So I'm ok with the current names.
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
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-hackers@postgresql.org
Cc: masao.fujii@oss.nttdata.com, michael@paquier.xyz, alvherre@2ndquadrant.com, pgsql-hackers@lists.postgresql.org, thomas.munro@gmail.com
Subject: Re: pg_stat_wal_receiver and flushedUpto/writtenUpto
In-Reply-To: <c049ffcf-d2fe-90f7-c8ba-0741035aa6a7@oss.nttdata.com>
* 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