diff options
| author | Michael Paquier <michael@paquier.xyz> | 2018-12-09 16:35:06 +0900 |
|---|---|---|
| committer | Michael Paquier <michael@paquier.xyz> | 2018-12-09 16:35:06 +0900 |
| commit | 7fee252f6fbf78ca5e50ee591573d59f98e75d37 (patch) | |
| tree | 83d0719d6dc9fa454da312d3056a6b5c6e30cae4 /doc/src | |
| parent | 1f66c657f2b4eb55c68593d5c14256115aa6a0ea (diff) | |
| download | postgresql-7fee252f6fbf78ca5e50ee591573d59f98e75d37.tar.gz postgresql-7fee252f6fbf78ca5e50ee591573d59f98e75d37.zip | |
Add timestamp of last received message from standby to pg_stat_replication
The timestamp generated by the standby at message transmission has been
included in the protocol since its introduction for both the status
update message and hot standby feedback message, but it has never
appeared in pg_stat_replication. Seeing this timestamp does not matter
much with a cluster which has a lot of activity, but on a mostly-idle
cluster, this makes monitoring able to react faster than the configured
timeouts.
Author: MyungKyu LIM
Reviewed-by: Michael Paquier, Masahiko Sawada
Discussion: https://postgr.es/m/1657809367.407321.1533027417725.JavaMail.jboss@ep2ml404
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/monitoring.sgml | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml index 40e4298cf4e..96bcc3a63be 100644 --- a/doc/src/sgml/monitoring.sgml +++ b/doc/src/sgml/monitoring.sgml @@ -1920,6 +1920,11 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i </itemizedlist> </entry> </row> + <row> + <entry><structfield>reply_time</structfield></entry> + <entry><type>timestamp with time zone</type></entry> + <entry>Send time of last reply message received from standby server</entry> + </row> </tbody> </tgroup> </table> |