Re: [HACKERS] Logical replication: stuck spinlock atReplicationSlotRelease

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: [HACKERS] Logical replication: stuck spinlock atReplicationSlotRelease
Дата
Msg-id c252108d-5652-b5fd-4ec2-7dbfb92866bb@2ndquadrant.com
обсуждение исходный текст
Ответ на Re: [HACKERS] Logical replication: stuck spinlock atReplicationSlotRelease  (Andres Freund <andres@anarazel.de>)
Ответы Re: [HACKERS] Logical replication: stuck spinlock at ReplicationSlotRelease  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [HACKERS] Logical replication: stuck spinlock atReplicationSlotRelease  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Список pgsql-hackers
Дерево обсуждения 
On 6/23/17 16:15, Andres Freund wrote:
> On 2017-06-23 13:26:58 -0400, Alvaro Herrera wrote:
>> Hmm, so for instance in LogicalIncreaseRestartDecodingForSlot() we have
>> some elog(DEBUG1) calls with the slot spinlock held.  That's probably
>> uncool.
> 
> It definitely is not cool, rather daft even (it's probably me who wrote
> that).  No idea why I've done it like that, makes no sense.

Do you want to take a look at move those elog calls around a bit?  That
should do it.

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

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

Предыдущее
От: Stephen Frost
Дата:
Сообщение: Re: [HACKERS] pg_terminate_backend can terminate background workersand autovacuum launchers
Следующее
От: Peter Eisentraut
Дата:
Сообщение: Re: [HACKERS] Get stuck when dropping a subscription duringsynchronizing table