Tracking replication slot "blockings"

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Tracking replication slot "blockings"
Date: 2014-04-16 16:51:41
Message-ID: CABUevEyD1Q_MGQ6dcwy1yiV8J8wqXXTw+-dY+7C3zUyj-pJS_w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I'm thinking it could be interesting to know how many times (or in some
other useful unit than "times" - how often) a specific replication slot has
"blocked" xlog rotation. Since this AFAIK only happens during checkpoints,
it seems it should be "reasonably cheap" to track? It would serve as an
indicator of which slave(s) are having enough trouble keeping up to
potentially cause issues.

Not having looked at that code at all yet, would this be something that's
simple to add?

Or is it a silly idea? :)

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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Marco Atzeri 2014-04-16 16:55:31 Re: test failure on latest source
Previous Message Robert Haas 2014-04-16 16:42:40 Re: Ctrl+C from sh can shut down daemonized PostgreSQL cluster