pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Rajesh Kumar Mallah <mallah@trade-india.com>
To: Tsirkin Evgeny <tsurkin@mail.jct.ac.il>
Cc: pgsql-admin@postgresql.org
Subject: Re: '<IDLE> in transaction' problem in mod_perl/DBI/DBD-Pg
Date: Mon, 25 Oct 2004 16:56:18 +0530
Message-ID: <417CE2DA.4080804@trade-india.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0410250931130.15606@p-roman.jct.ac.il>
References: <417C912E.3080109@trade-india.com>
	<Pine.LNX.4.58.0410250931130.15606@p-roman.jct.ac.il>

Hi,


Somehow those pids automatically got terminated
and my problem was solved. I did not issue any kill as i
do not have access to  the server.

curious how it happened any idea??

Regds
mallah.



Tsirkin Evgeny wrote:

>On Mon, 25 Oct 2004, Rajesh Kumar Mallah wrote:
>
>  
>
>>Hi,
>>
>>We run our webserver using mod_perl and perl/DBI/DBD-Pg .
>>I have observed that most of the pg backends that block other queries
>>are in '<IDLE> in transaction' state.  Usually sending a -INT or -TERM
>>to such blocking backends solve the problem.
>>
>>My question is
>>
>>1. Are there some precuation to be taken in perl/DBI programming
>>    in mod_perl environment to avoid backends getting into '<IDLE> in 
>>transaction'
>>    mode?
>>    
>>
>Yes.Be very carefull with transaction - that is:
>[1] try the backends that are entering transactions to make the updates in 
>the same order ,so you will not get a deadlock.(read the manual for more
>info).
>[2] try to make the transactions as short as you can,if you don't need 
>transactions - don't use it ,turn the Autocommit on!
>
>[3] befor your updates /deletes it sometimes VERY usefull to do a select 
>for update which will lock the rows befor entering the transactions ,that
>will avoid two backends updating same rows to enter transaction and ,so
>avoid deadlocks.
>
>  
>
>>2. Is it advisable/safe to run a daemon that TERMs such blocking backend
>>    at regular interval.
>>    
>>
>
>I don't think so - that will not let postgres end the transactions and 
>so no changes will be applied,more then that - this may kill the all the
>postgres processes .
>
>  
>
>>3. Most Importantly , If a do not have access to to the host is it 
>>possible to
>>    TERMinate such backeds from  psql>
>>    
>>
>
>Don't know.
>  
>
>>Regds
>>Mallah.
>>
>>
>>---------------------------(end of broadcast)---------------------------
>>TIP 5: Have you checked our extensive FAQ?
>>
>>               http://www.postgresql.org/docs/faqs/FAQ.html
>>
>>    
>>
>
>  
>


-- 

regds
Mallah.

Rajesh Kumar Mallah
+---------------------------------------------------+
| Tradeindia.com  (3,11,246) Registered Users 	    | 
| Indias' Leading B2B eMarketPlace                  |
| http://www.tradeindia.com/			    |
+---------------------------------------------------+




view thread (5+ messages)  latest in thread

Message-ID: <417CE2DA.4080804@trade-india.com>
Permalink:  ../417CE2DA.4080804@trade-india.com/
Also on:    postgresql.org/message-id/417CE2DA.4080804@trade-india.com

 · 

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: mallah@trade-india.com, tsurkin@mail.jct.ac.il
  Subject: Re: '<IDLE> in transaction' problem in mod_perl/DBI/DBD-Pg
  In-Reply-To: <417CE2DA.4080804@trade-india.com>
  References: <417C912E.3080109@trade-india.com> <Pine.LNX.4.58.0410250931130.15606@p-roman.jct.ac.il> <417CE2DA.4080804@trade-india.com>

* 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