On Thu, May 24, 2012 at 3:36 PM, Sergey Koposov <kopo...@ast.cam.ac.uk> wrote: > Hi, > > > On Thu, 24 May 2012, Robert Haas wrote: >> >> Not sure. It might be some other LWLock, but it's hard to tell which >> one from the information provided. > > > If you could tell what's the best way to find out the info that you need, > then I could run it reasonably quickly.
Add #define LWLOCK_STATS near the top of: src/backend/storage/lmgr/lwlock.c and recompile and run a reduced-size workload. When the processes exits, they will dump a lot of data about LWLock usage to the logfile. Generally the LWLock with the most blocks on it will be the main culprit. Cheers, Jeff -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
