Re: Stuck processes, viewing the queries inside

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: bryan(at)netmeme(dot)org
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Stuck processes, viewing the queries inside
Date: 2003-11-20 05:35:02
Message-ID: 1457.1069306502@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Bryan Field-Elliot <bryan_lists(at)netmeme(dot)org> writes:
> We have a running server (v7.3) which, over time, seems to accumulate a
> bunch of "stuck" PostgreSQL instances which appear to be dead inside of
> a transaction. For example, "ps" reveals many of these:

> postgres 17683 0.0 0.4 7376 1032 ? S Nov13 0:21 postgres:
> bryan sourceid 127.0.0.1 idle in transaction

"idle in transaction" means the backend is waiting for its connected
client to issue another command. I don't think it's Postgres that you
need to be investigating ...

> I can't see a query for "given a process ID currently
> in a transaction, show me all the queries which have been run in it so
> far".

There is no such query, but you could try turning on query logging and
then studying the postmaster log.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Shridhar Daithankar 2003-11-20 06:12:42 Re: Humor me: Postgresql vs. MySql (esp. licensing)
Previous Message K. Deepa 2003-11-20 05:31:01 Is it possible to find a size of a table