From 311bcfc6b3acdd6fd152798c7f287ddf74fa2a98 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Tue, 16 Apr 2024 21:46:48 +0200 Subject: Adding upstream version 15.4. Signed-off-by: Daniel Baumann --- .../sgml/html/logical-replication-monitoring.html | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 doc/src/sgml/html/logical-replication-monitoring.html (limited to 'doc/src/sgml/html/logical-replication-monitoring.html') diff --git a/doc/src/sgml/html/logical-replication-monitoring.html b/doc/src/sgml/html/logical-replication-monitoring.html new file mode 100644 index 0000000..108ffa0 --- /dev/null +++ b/doc/src/sgml/html/logical-replication-monitoring.html @@ -0,0 +1,20 @@ + +31.8. Monitoring
31.8. Monitoring
Prev UpChapter 31. Logical ReplicationHome Next

31.8. Monitoring

+ Because logical replication is based on a similar architecture as + physical streaming replication, + the monitoring on a publication node is similar to monitoring of a + physical replication primary + (see Section 27.2.5.2). +

+ The monitoring information about subscription is visible in + + pg_stat_subscription. + This view contains one row for every subscription worker. A subscription + can have zero or more active subscription workers depending on its state. +

+ Normally, there is a single apply process running for an enabled + subscription. A disabled subscription or a crashed subscription will have + zero rows in this view. If the initial data synchronization of any + table is in progress, there will be additional workers for the tables + being synchronized. +

Prev Up Next
31.7. Architecture Home 31.9. Security
\ No newline at end of file -- cgit v1.2.3