Re: [HACKERS] Logical replication: stuck spinlock atReplicationSlotRelease

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: [HACKERS] Logical replication: stuck spinlock atReplicationSlotRelease
Дата
Msg-id 28c6bd45-13f4-9244-7d1a-c1e80fd33ae9@2ndquadrant.com
обсуждение исходный текст
Ответ на Re: [HACKERS] Logical replication: stuck spinlock atReplicationSlotRelease  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Список pgsql-hackers
On 6/23/17 16:10, Peter Eisentraut wrote:
>> Hmm, so for instance in LogicalIncreaseRestartDecodingForSlot() we have
>> some elog(DEBUG1) calls with the slot spinlock held.  That's probably
>> uncool.

> Removing the call you pointed out doesn't make a difference, but it's
> possibly something similar.

Correction: The fault actually is in that function.  I had only looked
at the "if" branch, but it was the "else" branch that triggered the
problem in this run.  If I remove those elog calls, everything works
smoothly.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



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

Предыдущее
От: Thomas Munro
Дата:
Сообщение: Re: [HACKERS] Small bug in replication lag tracking
Следующее
От: Stephen Frost
Дата:
Сообщение: Re: [HACKERS] pg_terminate_backend can terminate background workersand autovacuum launchers