Skip site navigation (1) Skip section navigation (2)

Re: Getting previous statements executed a backend currenly in an <idle> in transaction state.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Rajesh Kumar Mallah" <mallah(dot)rajesh(at)gmail(dot)com>
Cc: "Lista Postgres" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Getting previous statements executed a backend currenly in an <idle> in transaction state.
Date: 2007-01-22 06:44:58
Message-ID: 6524.1169448298@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-admin
"Rajesh Kumar Mallah" <mallah(dot)rajesh(at)gmail(dot)com> writes:
> This issue has been posted before also but this time i wanted
> to know, if it is possible to know what statements have been
> executed by the backend in the same transaction which is currently
> idle. this can probably help us in identifying the faulty application
> code.

> in past we had set a logging prefix in guc and used grep to digout
> the statements but that was logging all statements which was
> probably not a good idea in production environment. Can some
> one suggest if anything else is readily available.

AFAICS, log_statement and friends are much cheaper than any other
alternative could be.

			regards, tom lane

In response to

Responses

pgsql-admin by date

Next:From: Rajesh Kumar MallahDate: 2007-01-22 08:05:59
Subject: Re: Getting previous statements executed a backend currenly in an <idle> in transaction state.
Previous:From: Rajesh Kumar MallahDate: 2007-01-22 06:11:01
Subject: Re: Getting previous statements executed a backend currenly in an <idle> in transaction state.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group