Re: Recovery conflict monitoring

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Recovery conflict monitoring
Date: 2010-12-27 13:39:02
Message-ID: AANLkTimTaR5wBpkF-17t1DtBv8v3qwfnXxznsmq4RYg2@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Dec 23, 2010 at 13:09, Magnus Hagander <magnus(at)hagander(dot)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 Content-Type Size
recovery_conflict_stat.patch text/x-patch 17.7 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2010-12-27 13:41:27 Re: Streaming replication as a separate permissions
Previous Message Simon Riggs 2010-12-27 13:25:29 Re: Streaming replication as a separate permissions