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

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(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-11-01 18:36:02
Message-ID: 3222e35a-a459-7fbd-6468-914ae01d873d@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-general

On 7/27/17 16:14, Jeff Janes wrote:
> On Wed, Jul 26, 2017 at 1:44 AM, Michael Paquier
> <michael(dot)paquier(at)gmail(dot)com <mailto:michael(dot)paquier(at)gmail(dot)com>> wrote:
>
> On Mon, Jul 24, 2017 at 9:08 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com
> <mailto:jeff(dot)janes(at)gmail(dot)com>> wrote:
> > On Sun, Jul 16, 2017 at 8:47 AM, Michael Paquier <michael(dot)paquier(at)gmail(dot)com <mailto:michael(dot)paquier(at)gmail(dot)com>>
> > wrote:
> >> What do you think about the patch attached?
> >
> > Looks OK.  Should it mention specifically "On a hot standby" rather than "On
> > a standby"?  Otherwise people might be left confused on how they are
> > supposed to do this on a generic standby.  It is the kind of thing which is
> > obvious once you know it, but confusing the first time you encounter it.
>
> Yes, right. Let's update as you suggest.
>
>
> new version looks good.

committed

I changed to links to xrefs, which automatically generated the correct
target texts.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Scott Marlowe 2017-11-01 18:59:11 explain analyze output: 0 rows, 1M loopa
Previous Message Tom Lane 2017-11-01 15:25:57 Re: the database system is shutting down - terminating walsender process due to replication timeout