| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Tracking replication slot "blockings" |
| Date: | 2014-04-16 17:12:50 |
| Message-ID: | 20140416171250.GQ17874@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2014-04-16 19:09:09 +0200, Magnus Hagander wrote:
> On Wed, Apr 16, 2014 at 6:56 PM, Andres Freund <andres(at)2ndquadrant(dot)com>wrote:
> > The xlog removal code just check the "global minimum" required LSN - it
> > doesn't check the individual slots. So you'd need to add a bit more code
> > to that location. But it'd be easy.
> >
>
> Do we have statistics there somewhere - how often that global minimum
> blocks something? That on it's own might be a start :)
Nope. Check xlog.c:KeepLogSeg(), it's pretty simple stuff ;). It's the
same place where wal_keep_segments is enforced...
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Claudio Freire | 2014-04-16 17:26:45 | Re: Clock sweep not caching enough B-Tree leaf pages? |
| Previous Message | Magnus Hagander | 2014-04-16 17:09:09 | Re: Tracking replication slot "blockings" |