Re: [Todo item] Add entry creation timestamp column topg_stat_replication - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [Todo item] Add entry creation timestamp column topg_stat_replication
Date
Msg-id 20181122075321.GJ3369@paquier.xyz
Whole thread Raw
In response to Re: [Todo item] Add entry creation timestamp column to pg_stat_replication  (Masahiko Sawada <sawada.mshk@gmail.com>)
Responses RE: [Todo item] Add entry creation timestamp column topg_stat_replication  ("myungkyu.lim" <myungkyu.lim@samsung.com>)
List pgsql-hackers
On Thu, Nov 15, 2018 at 05:33:26PM +0900, Masahiko Sawada wrote:
> Yeah, I also agree with 'reply_time'. But please also note that we had
> the discussion when there is not the similar system catalogs and
> fields. Now that we have them it might be worth to consider to follow
> the existing name for consistency.

The fields in pg_stat_wal_receiver are named after their respective
fields.  Now if you look at the fields from pg_stat_replication, you
have those from the standby:
sent_lsn => Last write-ahead log location sent on this connection
write_lsn => Last write-ahead log location written to disk by this
standby server
flush_lsn => Last write-ahead log location flushed to disk by
this standby server
replay_lsn => Last write-ahead log location replayed into the
database on this standby server

So to keep the brand consistent, reply_time looks like the best choice
as Sawada-san suggests?
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: Tid scan improvements
Next
From: Adrien NAYRAT
Date:
Subject: Re: performance statistics monitoring without spamming logs