From: Edmar Wiggers <edmar@brasmap.com>
To: pgsql-sql@postgreSQL.org
Subject: "too big" transactions
Date: Thu, 19 Oct 2000 22:59:54 -0200
Message-ID: <NEBBIAKDCDHFGJMLHCKIAEHJCAAA.edmar@brasmap.com> (raw)
In-Reply-To: <12798.971999349@sss.pgh.pa.us>
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.
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: edmar@brasmap.com
Subject: Re: "too big" transactions
In-Reply-To: <NEBBIAKDCDHFGJMLHCKIAEHJCAAA.edmar@brasmap.com>
References: <12798.971999349@sss.pgh.pa.us> <NEBBIAKDCDHFGJMLHCKIAEHJCAAA.edmar@brasmap.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