Re: Recovery conflict monitoring - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Recovery conflict monitoring
Date
Msg-id AANLkTimTaR5wBpkF-17t1DtBv8v3qwfnXxznsmq4RYg2@mail.gmail.com
Whole thread Raw
In response to Recovery conflict monitoring  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Recovery conflict monitoring  (Simon Riggs <simon@2ndQuadrant.com>)
Re: Recovery conflict monitoring  (Greg Smith <greg@2ndquadrant.com>)
List pgsql-hackers
On Thu, Dec 23, 2010 at 13:09, Magnus Hagander <magnus@hagander.net> wrote:
> This patch adds counters and views to monitor hot standby generated
> recovery conflicts. It extends the pg_stat_database view with one
> column with the total number of conflicts, and also creates a new view
> pg_stat_database_conflicts that contains a breakdown of exactly what
> caused the conflicts.
>
> Documentation still pending, but comments meanwhile is of course appreciated ;)

Heikki pointed out over IM that it's pointless to count stats caused
by recovery conflict with drop database - since we drop the stats
record as soon as it arrives anyway. Here's an updated patch that
removes that, and also adds some documentation.

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

Attachment

pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Streaming replication as a separate permissions
Next
From: Magnus Hagander
Date:
Subject: Re: Streaming replication as a separate permissions