pg.ddx.io pgsql-admin@postgresql.org mailing list archivehelp / color / mirror / Atom feed
UNDO 2+ messages / 2 participants [nested] [flat]
* UNDO @ 2004-06-21 16:09 Carlos Benkendorf <chbenkendorf@yahoo.com> 2004-06-22 01:05 ` Re: UNDO Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 1 reply; 2+ messages in thread From: Carlos Benkendorf @ 2004-06-21 16:09 UTC (permalink / raw) To: pgsql-admin Hi, In 7.4 manual is written than UNDO is not implemented. What it really means? When should PostgreSQL do an UNDO? Are not all data only written to disk when it is committed? Why should Postgresql do an undo? Thanks in advance! ______________________________________________________________________ Yahoo! Mail - agora com 100MB de espaço, anti-spam e antivírus grátis! http://br.info.mail.yahoo.com/ ^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: UNDO 2004-06-21 16:09 UNDO Carlos Benkendorf <chbenkendorf@yahoo.com> @ 2004-06-22 01:05 ` Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 0 replies; 2+ messages in thread From: Tom Lane @ 2004-06-22 01:05 UTC (permalink / raw) To: Carlos Benkendorf <chbenkendorf@yahoo.com>; +Cc: pgsql-admin =?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 ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2004-06-22 01:05 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2004-06-21 16:09 UNDO Carlos Benkendorf <chbenkendorf@yahoo.com> 2004-06-22 01:05 ` Tom Lane <tgl@sss.pgh.pa.us>
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