Re: Tracking replication slot "blockings"

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: Tracking replication slot "blockings"
Дата
Msg-id 20140416171250.GQ17874@awork2.anarazel.de
обсуждение исходный текст
Ответ на Re: Tracking replication slot "blockings"  (Magnus Hagander <magnus@hagander.net>)
Список 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@2ndquadrant.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



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Magnus Hagander
Дата:
Сообщение: Re: LDAP: bugfix and deprecated OpenLDAP API
Следующее
От: Claudio Freire
Дата:
Сообщение: Re: Clock sweep not caching enough B-Tree leaf pages?