X-Original-To: pgsql-interfaces@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 1E4E64758BD for ; Tue, 25 Feb 2003 13:56:47 -0500 (EST) Received: from postgresql.org ([64.49.215.8]) by localhost (postgresql.org [64.49.215.8:10024]) (amavisd-new) with SMTP id 61624-05 for ; Tue, 25 Feb 2003 13:56:16 -0500 (EST) Received: from sax.newsnipple.com (unknown [64.71.188.75]) by postgresql.org (Postfix) with ESMTP id 8AA28475A8D for ; Tue, 25 Feb 2003 13:51:23 -0500 (EST) Received: by sax.newsnipple.com (Postfix, from userid 500) id D0CBA430DC; Tue, 25 Feb 2003 10:46:38 -0800 (PST) Date: Tue, 25 Feb 2003 10:46:38 -0800 From: Adam Haberlach To: pgsql-interfaces@postgresql.org Subject: perl dbd libraries keeping transactions open? Message-ID: <20030225104638.A7643@newsnipple.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i X-Virus-Scanned: by amavisd-new X-Archive-Number: 200303/3 X-Sequence-Number: 3752 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 |