> >> 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.
I see "XLogWrite: new log file created..." in postmaster' log -
backend writes this after releasing 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?
How to synchronize with checkpoint-er if wal_files > 0?
And you know - I've run same tests on ~ Mar 9 snapshot
without any problems.
Vadim
