Re: [PERFORM] Very slow planning performance on partition table

[Rural Hunter]

在 2014/7/29 1:29, Jeff Janes 写道: 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 Yes. I have a lot of connections and they maybe coming together and doing the same update statement without partition key on the partition table.