Re: Monitoring of a hot standby with a largely idle master

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Monitoring of a hot standby with a largely idle master
Date: 2017-07-16 15:47:20
Views: Raw Message | Whole Thread | Download mbox
Lists: pgsql-general

On Fri, Jul 14, 2017 at 9:11 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> On Thu, Jul 13, 2017 at 10:38 AM, Michael Paquier
> <michael(dot)paquier(at)gmail(dot)com> wrote:
>> On Thu, Jul 13, 2017 at 7:23 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
>> >
>> > I think that pg_stat_wal_receiver should be crossreferenced in
>> >, near the
>> > same
>> > place which it crossreferences table 9-79. That would make it more
>> > discoverable.
>> Hm. Hot standby may not involve streaming replication. What about a
>> paragraph here instead?
>> In the monitoring subsection, we could tell that on a standby the WAL
>> receiver status can be retrieved from this view when changes are
>> streamed. What do you think?
> That works for me.

What do you think about the patch attached?

You can retrieve a list of WAL sender processes via the
- <link linkend="monitoring-stats-views-table">
+ <link linkend="monitoring-stats-dynamic-views-table">
<literal>pg_stat_replication</></link> view. Large differences between
In the previous paragraph I have noticed that the link reference is
incorrect. pg_stat_replication is listed under

Attachment Content-Type Size
walreceiver-doc.patch application/octet-stream 1.4 KB

In response to


Browse pgsql-general by date

  From Date Subject
Next Message Andreas Joseph Krogh 2017-07-17 10:34:04 Storing LOs outside the database and having a proper cleanup-mechanism to prevent dangling files
Previous Message Devrim Gündüz 2017-07-16 11:39:06 Re: Failed DNF dependency in Fedora