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

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

From: "Rajesh Kumar Mallah" <mallah(dot)rajesh(at)gmail(dot)com>
To: "Lista Postgres" <pgsql-admin(at)postgresql(dot)org>
Subject: Getting previous statements executed a backend currenly in an <idle> in transaction state.
Date: 2007-01-22 04:25:16
Message-ID: a97c77030701212025x3eaff03bq46935a5072cb6e19@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-admin
Dear Friends,

Due to some bug(s) in our apps , in a mod_perl environment
many backend remain in <idle> in transaction state. This
backends sometimes block other statements in batch
processes which in turn blocks access to some production
tables.

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.


regds
mallah.

Responses

pgsql-admin by date

Next:From: Umesh ShastryDate: 2007-01-22 05:42:43
Subject: Re: Getting previous statements executed a backend currenly in an <idle> in transaction state.
Previous:From: Tom LaneDate: 2007-01-21 18:10:18
Subject: Re: Can I copy data file and use it with other version of Postgresql

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