Re: Nested transactions: low level stuff

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Vadim Mikheev" <vmikheev(at)reveredata(dot)com>
Cc: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Manfred Koizar" <mkoi-pg(at)aon(dot)at>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Nested transactions: low level stuff
Date: 2003-03-20 04:53:53
Message-ID: 20452.1048136033@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Vadim Mikheev" <vmikheev(at)reveredata(dot)com> writes:
>> Given all the flak we got about WAL growth during the time we had that
>> code enabled, I think there's no chance that UNDO will be the preferred
>> path. It's not workable with big transactions.

> Somehow it's working in other DB systems.

Isn't limited UNDO segment size one of the most-hated management
problems for Oracle databases? I don't see why we should want to
duplicate one of their worst problems.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2003-03-20 04:54:24 Re: A bad behavior under autocommit off mode
Previous Message Bruce Momjian 2003-03-20 04:51:59 Re: [HACKERS] loading libraries on Postmaster startup