On Sat, Mar 31, 2012 at 1:58 PM, Greg Stark <st...@mit.edu> wrote: > On Sat, Mar 31, 2012 at 4:41 AM, Robert Haas <robertmh...@gmail.com> wrote: >> But I didn't think we were ever supposed to hold content >> locks for that long. > > Isn't that lock held while doing visibility checks? What about I/O > waiting for a clog page to be read?
So what we should be logging is the list of lwlocks held when the lock wait occurred. That would differentiate call paths somewhat better than just looking at the current lock request. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
