Postgres Pro
Downloads
Home   >   mailing lists

Re: [HACKERS] Logical replication: stuck spinlock atReplicationSlotRelease - Mailing list pgsql-hackers

From Andres Freund
Subject Re: [HACKERS] Logical replication: stuck spinlock atReplicationSlotRelease
Date
Msg-id 20170623201509.35ofoplznwmb5tcf@alap3.anarazel.de
Whole thread Raw
In response to Re: [HACKERS] Logical replication: stuck spinlock atReplicationSlotRelease  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: [HACKERS] Logical replication: stuck spinlock atReplicationSlotRelease  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
Tree view 
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.

Andres Freund

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] Logical replication: stuck spinlock atReplicationSlotRelease
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] initdb initalization failure for collation "ja_JP"