Peter Eisentraut <peter.eisentr...@2ndquadrant.com> writes:
> On 6/23/17 13:26, Alvaro Herrera wrote:
>> Hmm, so for instance in LogicalIncreaseRestartDecodingForSlot() we have
>> some elog(DEBUG1) calls with the slot spinlock held. That's probably
>> uncool.
> I can reproduce the issue with --client-min-messages=debug2 or debug1,
> but it doesn't appear with the default settings. I don't always get the
> "stuck spinlock" message, but it hangs badly pretty reliably after two
> or three rounds of erroring.
> Removing the call you pointed out doesn't make a difference, but it's
> possibly something similar.
Maybe some function invoked in a debug ereport accesses shared memory
or takes locks (eg, for catalog access)?
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
