Mike Richards <mrmikerich@gmail.com> writes:
> PANIC: XX000: stuck spinlock (0x4035a0a0) detected at lwlock.c:242
> ...
> LOG: 00000: server process (PID 20195) was terminated by signal 11
> ...
> FATAL: semctl(0, 0, SETVAL, 0) failed: Identifier removed
If you were getting just one of these then I might think you'd come
across a previously unknown PG bug. Given the variety of failure modes,
though, I'm strongly inclined to suspect that the common root cause is
flaky RAM. Time to get out memtest86 or some such tool.
regards, tom lane
