Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id D085F9FB320 for ; Mon, 22 Jan 2007 02:16:07 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 65940-07 for ; Mon, 22 Jan 2007 02:16:00 -0400 (AST) X-Greylist: delayed 00:30:51.273855 by SQLgrey-1.7.4 Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 563DE9FB564 for ; Mon, 22 Jan 2007 02:16:01 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 Received: from tomato.gtsgraphics.com (tomato.lax.techbooks.com [208.179.178.60]) by svr4.postgresql.org (Postfix) with ESMTP id AC5875AF8A7 for ; Mon, 22 Jan 2007 05:45:05 +0000 (GMT) Received: from delhimail-ph.del.techbooks.com (delhimail-ph.del.techbooks.com [192.168.180.182] (may be forged)) by tomato.gtsgraphics.com (8.12.10+Sun/8.12.10) with ESMTP id l0M5ioPF023785; Sun, 21 Jan 2007 21:44:52 -0800 (PST) Received: from mmkservdev (mmkservdev.del.techbooks.com [192.168.181.3]) by delhimail-ph.del.techbooks.com (8.12.10+Sun/8.9.2) with SMTP id l0M5aZVi015182; Mon, 22 Jan 2007 11:06:36 +0530 (IST) Message-ID: <004b01c73de8$262e3d20$03b5a8c0@mmkservdev> Reply-To: "Umesh Shastry" From: "Umesh Shastry" To: "Rajesh Kumar Mallah" , "Lista Postgres" References: Subject: Re: Getting previous statements executed a backend currenly in an in transaction state. Date: Mon, 22 Jan 2007 11:12:43 +0530 Organization: TechBooks MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0046_01C73E16.3CAD9540" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.3790.2826 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.2826 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.271 tagged_above=0 required=5 tests=BAYES_50, FORGED_RCVD_HELO, HTML_50_60, HTML_MESSAGE X-Spam-Level: X-Archive-Number: 200701/187 X-Sequence-Number: 24343 This is a multi-part message in MIME format. ------=_NextPart_000_0046_01C73E16.3CAD9540 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable This may help you... http://archives.postgresql.org/pgsql-announce/2006-01/msg00007.php ----- Original Message -----=20 From: Rajesh Kumar Mallah=20 To: Lista Postgres=20 Sent: Monday, January 22, 2007 9:55 AM Subject: [ADMIN] Getting previous statements executed a backend = currenly in an in transaction state. Dear Friends, Due to some bug(s) in our apps , in a mod_perl environment many backend remain in 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 ------=_NextPart_000_0046_01C73E16.3CAD9540 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
This may help you...
 
http://archives.postgresql.org/pgsql-announce/2006-01/msg00007.php=
 
 
----- Original Message -----
From:=20 Rajesh=20 Kumar Mallah
Sent: Monday, January 22, 2007 = 9:55=20 AM
Subject: [ADMIN] Getting = previous=20 statements executed a backend currenly in an <idle> in = transaction=20 state.

Dear Friends,

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

This = issue=20 has been posted before also but this time i wanted
to know, if it = is=20 possible to know what statements have been
executed by the backend = in the=20 same transaction which is currently
idle. this can probably help us = in=20 identifying the faulty application
code.

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


regds
mallah.

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

         &n= bsp;    =20 http://archives.postgresql.org
------=_NextPart_000_0046_01C73E16.3CAD9540--