From: Tom Lane <tgl@sss.pgh.pa.us>
To: Carlos Benkendorf <chbenkendorf@yahoo.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: UNDO
Date: Mon, 21 Jun 2004 21:05:29 -0400
Message-ID: <8305.1087866329@sss.pgh.pa.us> (raw)
In-Reply-To: <20040621160924.42151.qmail@web60305.mail.yahoo.com>
References: <20040621160924.42151.qmail@web60305.mail.yahoo.com>
=?iso-8859-1?q?Carlos=20Benkendorf?= <chbenkendorf@yahoo.com> writes:
> In 7.4 manual is written than UNDO is not implemented.
> What it really means?
Not much. It's unlikely that we ever will implement UNDO in the sense
that passage is talking about --- which is to say, reversing out the
effects of a failed transaction by scanning the WAL log backwards.
Pretty much all the current pghackers agree that MVCC is a better
approach.
MVCC means that you have to do periodic VACUUMs to get rid of cruft
from failed transactions, so it's not like it's a zero-cost substitute
for UNDO. But the nice thing about it is that the overhead
is paid in a background maintenance task, rather than being something
that has to happen in a foreground server task whenever a transaction
fails. Cleaning up via UNDO means that live clients are waiting for
you to do the cleanup.
There used to be a contingent that thought we should switch to using
UNDO because Oracle does it that way and Oracle must be right. But
we've gained more self-confidence since, I think.
regards, tom lane
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-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, chbenkendorf@yahoo.com
Subject: Re: UNDO
In-Reply-To: <8305.1087866329@sss.pgh.pa.us>
References: <20040621160924.42151.qmail@web60305.mail.yahoo.com> <8305.1087866329@sss.pgh.pa.us>
* 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