Re: Psycopg/ZPsycopg open connection problem...

Stefan,

thank you for your file. 

We are currently working with a modified version of the product, provided by 
Federico, that has been reworked in order to remove some possible defects.

We have been able to see two different problems:

- the first, which was generates an "idle in transaction" problem, seems tied 
to the way Zope manages abort during error recovery. Basically, we had a SQL 
method that was invoked in the standard error message. This, due to Zope, 
leaves a transaction in the middle;

- the second generates lots of "idle in transaction" connections to postgres. 
This seems a much stranger bug. We have two potential causes:

        - the cache management. Perhaps the connection object is cached and it 
is not 
correctly removed from the cache;

        - the use of fetchmany. In our SQL code we use a limit clause, that 
generates 
a call to the fetchmany. Is this lefting behind some connection ?

We will investigate further.

Best regards.

Paolo


> Paolo,
>
> I have attached an alternative version of db.py that does not eat
> exceptions and logs its operations to the event.log. You may want to use it
> for debugging or even on the production site. No warranties of any kind ;-)
>
> Stefan
>
> At 02.02.2004 13:11 +0100, Paolo Bizzarri wrote:
> >Hi everyone,
> >
> >we have been able to reproduce the bug in Psycopg/ZPsycopg, so that if we
> > run a certain script we consistely obtain a connection to Postgresql
> > "idle in transaction".
>
> --
> ... a standard for copy protection is as premature as a standard
> for teleportation.                  Edward W. Felten, March 2002

-- 
Paolo Bizzarri - President - Icube S.r.l.
Address:        Via Ridolfi 15 - 56124 Pisa (PI), Italy
E-mail: p.bizzarri-QB8vYuOG93c@xxxxxxxxxxxxxxxx Web:    http://www.icube.it
Phone:  (+39) 050 97 02 07      Fax:    (+39) 050 31 36 588