pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: myungkyu.lim <myungkyu.lim@samsung.com>
To: 'Surafel Temesgen' <surafel3000@gmail.com>
Cc: 'PostgreSQL Hackers' <pgsql-hackers@postgresql.org>
Subject: RE: [Todo item] Add entry creation timestamp column to pg_stat_replication
Date: Thu, 15 Nov 2018 14:10:21 +0900
Message-ID: <003001d47ca1$8282dc20$87889460$@samsung.com> (raw)
In-Reply-To: <CALAY4q_hmeqd+E1kGOvDX5c22_3ns3m9O5i7qnaYmNdGm7pTqA@mail.gmail.com>
References: <CGME20180731085657epcms4p86e41bb64a978775023ef8cb77535ef44@epcms4p8>
	<1657809367.407321.1533027417725.JavaMail.jboss@ep2ml404>
	<CALAY4q_hmeqd+E1kGOvDX5c22_3ns3m9O5i7qnaYmNdGm7pTqA@mail.gmail.com>

Hi.
Thanks for your feedback.

> Can you explain the purpose of this feature more because now we have columns to report replication delay times like write_lag ,flush_lag and replay_lag that can use for similar purpose .

I think, time elapsed stats are very useful on DML query active system, 
but not present that stats on idle system - not query, or only select.

sent_lsn           | 0/5476C88
write_lsn          | 0/5476C88
flush_lsn          | 0/5476C88
replay_lsn         | 0/5476C88
write_lag          | 00:00:00.000055
flush_lag          | 00:00:00.000855
replay_lag         | 00:00:00.000914
sync_priority      | 0
sync_state         | async
last_msg_send_time | 2018-11-15 14:04:39.65889+09

state              | streaming
sent_lsn           | 0/5476CC0
write_lsn          | 0/5476CC0
flush_lsn          | 0/5476CC0
replay_lsn         | 0/5476CC0
write_lag          |
flush_lag          |
replay_lag         |
sync_priority      | 0
sync_state         | async
last_msg_send_time | 2018-11-15 14:05:02.935457+09

state              | streaming
sent_lsn           | 0/5476CC0
write_lsn          | 0/5476CC0
flush_lsn          | 0/5476CC0
replay_lsn         | 0/5476CC0
write_lag          |
flush_lag          |
replay_lag         |
sync_priority      | 0
sync_state         | async
last_msg_send_time | 2018-11-15 14:06:23.128947+09

This timestamp column is useful when react interval check and debugging on idle system.

Best regards,
Myungkyu, Lim





view thread (22+ messages)  latest in thread

Message-ID: <003001d47ca1$8282dc20$87889460$@samsung.com>
Permalink:  ../003001d47ca1$8282dc20$87889460$@samsung.com/
Also on:    postgresql.org/message-id/003001d47ca1$8282dc20$87889460$@samsung.com

 · 

reply

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: myungkyu.lim@samsung.com, surafel3000@gmail.com
  Subject: RE: [Todo item] Add entry creation timestamp column to pg_stat_replication
  In-Reply-To: <003001d47ca1$8282dc20$87889460$@samsung.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