Skip site navigation (1) Skip section navigation (2)

Re: perl dbd libraries keeping transactions open?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Adam Haberlach <adam(at)newsnipple(dot)com>
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: perl dbd libraries keeping transactions open?
Date: 2003-03-02 17:55:43
Message-ID: 18701.1046627743@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-interfaces
Adam Haberlach <adam(at)newsnipple(dot)com> writes:
> 	It seems that the implementation is for the libs to
> do a BEGIN on connect and after every transaction -- is
> this normal.  Is there a way to keep it from causing
> problems with vaccuums?

This is horrible practice for a number of reasons, not only its effect
on VACUUM.  Consider what you will get from now(), for example.  A new
BEGIN should only be issued when you are ready to issue the first
command of the next transaction.

If that hasn't been fixed yet in the dbd driver, I would recommend
fixing it there.

			regards, tom lane

In response to

Responses

pgsql-interfaces by date

Next:From: Ian BarwickDate: 2003-03-02 19:02:39
Subject: Re: perl dbd libraries keeping transactions open?
Previous:From: Tom LaneDate: 2003-03-02 17:48:29
Subject: Re: Darwin libpq link failing

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group