Jerry Gamache wrote: > Yes, I have PID in the logs now. Problem was observed around 13h30, > and there was no log output between 13h18 and 13h30. > There are messages for table_b (pid 18350) and table_c (pid 18406), > but none for table_a.
Eh, but according to the pg_locks snap you posted, the PID holding the table_b lock is (was?) 20490. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
