Received: from gw.acate.com.br ([200.215.17.89]) by hub.org (8.10.1/8.11.0) with ESMTP id e9K0vhJ92086 for ; Thu, 19 Oct 2000 20:57:44 -0400 (EDT) (envelope-from edmar@brasmap.com) Received: from ana ([192.168.1.13]) by gw.acate.com.br (8.9.3/8.9.3) with SMTP id WAA25743 for ; Thu, 19 Oct 2000 22:57:40 -0200 From: "Edmar Wiggers" To: Subject: "too big" transactions Date: Thu, 19 Oct 2000 22:59:54 -0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal In-Reply-To: <12798.971999349@sss.pgh.pa.us> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 X-Archive-Number: 200010/187 X-Sequence-Number: 1849 How does PostgreSQL handles a "too big" transaction? By that I mean a transaction which, after a certain point, there will be no way to roll back. On PgSQL, maybe that only happens when the disk fills. Is there a configurable "size" limit for a single transaction? In addition, what happens if the disk fills up? Postgres is able to roll back, right? I'm assuming you can prevent the disk from actually filling up (and crashing the whole server) by turning on quotas for the postgres super user, so that only pgsql would complain. Please correct me if I'm wrong.