On Wed, Sep 07, 2011 at 06:35:08PM -0400, Tom Lane wrote: > daveg <da...@sonic.net> writes: > > It does not seem restricted to pg_authid: > > 2011-08-24 18:35:57.445 24987 c23 apps ERROR: lock AccessShareLock on > > object 16403/2615/0 > > And I think I've seen it on other tables too. > > Hmm. 2615 = pg_namespace, which most likely is the first catalog > accessed by just about any SQL command that's going to access tables at > all, so I suspect that this is mostly just a "the first access failed" > thing and not something peculiar to pg_namespace. But we still don't > have a clue why the locks are not getting released by the previous > owner of the PGPROC slot. Have you trawled your logs to see if there's > any sign of any distress at all, shortly before the problem starts to > happen?
Will do, but its a pretty big haystack. Sure wish I knew what the needle looked like. ;-) -dg -- David Gould da...@sonic.net 510 536 1443 510 282 0869 If simplicity worked, the world would be overrun with insects. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
