summaryrefslogtreecommitdiff
path: root/src/include/replication
diff options
context:
space:
mode:
authorMichael Paquier2018-12-09 07:35:06 +0000
committerMichael Paquier2018-12-09 07:35:06 +0000
commit7fee252f6fbf78ca5e50ee591573d59f98e75d37 (patch)
tree83d0719d6dc9fa454da312d3056a6b5c6e30cae4 /src/include/replication
parent1f66c657f2b4eb55c68593d5c14256115aa6a0ea (diff)
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 'src/include/replication')
-rw-r--r--src/include/replication/walsender_private.h5
1 files changed, 5 insertions, 0 deletions
diff --git a/src/include/replication/walsender_private.h b/src/include/replication/walsender_private.h
index 4b904779361..53314b1fae5 100644
--- a/src/include/replication/walsender_private.h
+++ b/src/include/replication/walsender_private.h
@@ -75,6 +75,11 @@ typedef struct WalSnd
* SyncRepLock.
*/
int sync_standby_priority;
+
+ /*
+ * Timestamp of the last message received from standby.
+ */
+ TimestampTz replyTime;
} WalSnd;
extern WalSnd *MyWalSnd;