pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Umesh Shastry <ushastry@techbooks.com>
To: Rajesh Kumar Mallah <mallah.rajesh@gmail.com>
To: Lista Postgres <pgsql-admin@postgresql.org>
Subject: Re: Getting previous statements executed a backend currenly in an <idle> in transaction state.
Date: Mon, 22 Jan 2007 11:12:43 +0530
Message-ID: <004b01c73de8$262e3d20$03b5a8c0@mmkservdev> (raw)
References: <a97c77030701212025x3eaff03bq46935a5072cb6e19@mail.gmail.com>

This may help you...

http://archives.postgresql.org/pgsql-announce/2006-01/msg00007.php


  ----- Original Message ----- 
  From: Rajesh Kumar Mallah 
  To: Lista Postgres 
  Sent: Monday, January 22, 2007 9:55 AM
  Subject: [ADMIN] Getting previous statements executed a backend currenly in an <idle> in transaction state.


  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.

  ---------------------------(end of broadcast)---------------------------
  TIP 4: Have you searched our list archives?

                 http://archives.postgresql.org

view thread (5+ messages)  latest in thread

Message-ID: <004b01c73de8$262e3d20$03b5a8c0@mmkservdev>
Permalink:  ../004b01c73de8$262e3d20$03b5a8c0@mmkservdev/
Also on:    postgresql.org/message-id/004b01c73de8$262e3d20$03b5a8c0@mmkservdev

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: ushastry@techbooks.com, mallah.rajesh@gmail.com
  Subject: Re: Getting previous statements executed a backend currenly in an <idle> in transaction state.
  In-Reply-To: <004b01c73de8$262e3d20$03b5a8c0@mmkservdev>
  References: <a97c77030701212025x3eaff03bq46935a5072cb6e19@mail.gmail.com> <004b01c73de8$262e3d20$03b5a8c0@mmkservdev>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox