X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id F325ED1B266 for ; Mon, 21 Jun 2004 22:05:36 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 20489-06 for ; Tue, 22 Jun 2004 01:05:31 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id D4655D1B285 for ; Mon, 21 Jun 2004 22:05:26 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i5M15URg008306; Mon, 21 Jun 2004 21:05:30 -0400 (EDT) To: =?iso-8859-1?q?Carlos=20Benkendorf?= Cc: pgsql-admin@postgresql.org Subject: Re: UNDO In-reply-to: <20040621160924.42151.qmail@web60305.mail.yahoo.com> References: <20040621160924.42151.qmail@web60305.mail.yahoo.com> Comments: In-reply-to =?iso-8859-1?q?Carlos=20Benkendorf?= message dated "Mon, 21 Jun 2004 09:09:24 -0700" Date: Mon, 21 Jun 2004 21:05:29 -0400 Message-ID: <8305.1087866329@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200406/285 X-Sequence-Number: 13945 =?iso-8859-1?q?Carlos=20Benkendorf?= 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