pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Hans-Jürgen Schönig <hs@cybertec.at>
To: Nigel J. Andrews <nandrews@investsystems.co.uk>
Cc: pgsql-interfaces@postgresql.org
Cc: rlippan@remotelinux.com
Subject: Re: Problems with DBI transaction handling
Date: Fri, 07 Feb 2003 00:06:20 +0100
Message-ID: <3E42EA6C.3020107@cybertec.at> (raw)
References: <Pine.LNX.4.21.0302062140310.10564-100000@ponder.fairway2k.co.uk>

Hi ...

I am using:

DBI-1.21.tar.gz
DBD-Pg-1.01.tar.gz

my problem is that Perl complains about connections which are not closed 
properly and so forth but the main problem is that transactions don't 
seem to commit although the entire transaction seems to work fine. Maybe 
this has to do with SERIALIZABLE mode but it is hard to say. The only 
thing I am doing is a simple loop doing UPDATEs. I have been using DBI 
for a long time but this is the first time where transactions are used 
that heavily (normally we use Pg instead).

Maybe I should upgrade to a newer version but it seems as if this does 
not help in my case. I have no idea.

What we really need: A Perl module accessing LibEasy providing an 
interface to persistent database connections. I am using ApacheDBI at 
the moment (this seems to work well).

    Hans



Nigel J. Andrews wrote:

>On Tue, 4 Feb 2003, Hans-Jürgen Schönig wrote:
>
>  
>
>>Does anybody else have problems with DBI transaction handling? Since 
>>PostgreSQL 7.3 (most likely) the stuff seems to be broken. Errors occur 
>>even if autocommit is set properly and rollbacks are not performed the 
>>way it should be.
>>
>>Does anybody have similar problems? This is VERY annoying and should not 
>>happen.
>>The problem is: There is no other interface around providing persistent 
>>connections with Perl/Apache.
>>
>>Maybe it is worth thinking about a Perl implementation of LibEasy with 
>>Apache persistent connections.
>>    
>>
>
>Well I have wasted so much time recently, some of it spent trying to work out
>what DBI was doing. However, that was my lack of knowledge, although I'm still
>not convinced my tests don't now pass by luck. I'm also using a 7.2.3 server
>not 7.3 yet and it's not using the mod_perl persistent connection stuff.
>
>So in short, I'm not surprised you're having problems but unfortunately I can't
>say I experienced the same problem. Perhaps you could give a small test case
>that shows the problem as I'm sure DBI must have been tested against 7.3.
>
>
>  
>





-- 
*Cybertec Geschwinde u Schoenig*
Ludo-Hartmannplatz 1/14, A-1160 Vienna, Austria
Tel: +43/1/913 68 09; +43/664/233 90 75
www.postgresql.at <http://www.postgresql.at;, cluster.postgresql.at 
<http://cluster.postgresql.at;, www.cybertec.at 
<http://www.cybertec.at;, kernel.cybertec.at <http://kernel.cybertec.at;





view thread (6+ messages)  latest in thread

Message-ID: <3E42EA6C.3020107@cybertec.at>
Permalink:  ../3E42EA6C.3020107@cybertec.at/
Also on:    postgresql.org/message-id/3E42EA6C.3020107@cybertec.at

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-interfaces@postgresql.org
  Cc: hs@cybertec.at, nandrews@investsystems.co.uk, rlippan@remotelinux.com
  Subject: Re: Problems with DBI transaction handling
  In-Reply-To: <3E42EA6C.3020107@cybertec.at>

* 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