Overlooked your mentioning to timestamps in pg_stat_activity. What patterns do I need to look for there. Thanks Peter 2009/4/9 Kevin Grittner <Kevin.Grittner@xxxxxxxxxxxx>: > Péter Kovács <maxottovonstirlitz@xxxxxxxxx> wrote: >> postgres 14727 9868 0 22:34 ? 00:00:00 postgres: pkovacs >> chemaxon 127.0.0.1(12496) idle in transaction >> postgres 14735 9868 0 22:34 ? 00:00:00 postgres: pkovacs >> chemaxon 127.0.0.1(12497) idle in transaction >> postgres 14737 9868 0 22:34 ? 00:00:00 postgres: pkovacs >> chemaxon 127.0.0.1(12498) UPDATE waiting > > I would start by looking at pg_locks to see if your update is blocked > by one of the connections which is idle in a transaction. Any locks > won't be released until the idle transaction commits or rolls back. > Then look at pg_stat_activity to check timestamps. Be sure your > software doesn't have any code path which leaves things dangling. > (Since you seem to be using Java, I recommend proper use of > try/finally blocks to ensure resources are released.) > > -Kevi > -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
