From: Adam Haberlach <adam@newsnipple.com>
To: pgsql-interfaces@postgresql.org
Subject: perl dbd libraries keeping transactions open?
Date: Tue, 25 Feb 2003 10:46:38 -0800
Message-ID: <20030225104638.A7643@newsnipple.com> (raw)
I'm not sure if this is the right place, but I've got
a question and potential issue.
We've got a system consisting of several daemons written
in perl and a web interface, and we are having issues with
the nightly vacuums not doing anything. It seems that this
is happening because there is always a transaction held open
by the libraries.
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?
If this isn't the right place, or if anyone knows a
better place to ask this, let me know...
--
Adam Haberlach | "Because manholes are round."
adam@mediariffic.com |
http://mediariffic.com |
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: adam@newsnipple.com
Subject: Re: perl dbd libraries keeping transactions open?
In-Reply-To: <20030225104638.A7643@newsnipple.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