"Mikheev, Vadim" <vmikheev@SECTORBASE.COM> writes:
>> Got it at spin.c:156 with 50 clients doing inserts into
>> 50 tables (int4, text[1-256 bytes]).
>> -B 16384, -wal_buffers=256 (with default others wal params).
> SpinAcquire() ... but on which lock?
After a little bit of thought I'll bet it's ControlFileLockId.
Likely we shouldn't be using a spinlock at all for that, but the
short-term solution might be a longer timeout for this particular lock.
Alternatively, could we avoid holding that lock while initializing a
new log segment?
regards, tom lane