Tracking replication slot "blockings" - Mailing list pgsql-hackers

From Magnus Hagander
Subject Tracking replication slot "blockings"
Date
Msg-id CABUevEyD1Q_MGQ6dcwy1yiV8J8wqXXTw+-dY+7C3zUyj-pJS_w@mail.gmail.com
Whole thread Raw
Responses Re: Tracking replication slot "blockings"  (Andres Freund <andres@2ndquadrant.com>)
List 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/

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Ctrl+C from sh can shut down daemonized PostgreSQL cluster
Next
From: Marco Atzeri
Date:
Subject: Re: test failure on latest source