On Sun, Jul 27, 2014 at 9:28 AM, Tom Lane <t...@sss.pgh.pa.us> wrote:
> Rural Hunter <ruralhun...@gmail.com> writes: > >> Does that indicate something? seems it's waiting for some lock. > > Yeah, that's what the stack trace suggests. Have you looked into pg_locks > and pg_stat_activity to see which lock it wants and what's holding said > lock? > If it were waiting on a pg_locks lock, the semop should be coming from ProcSleep, not from LWLockAcquire, shouldn't it? I'm guessing he has a lot of connections, and each connection is locking each partition in shared mode in rapid fire, generating spin-lock or cache-line contention. Cheers, Jeff
