Re: Basic subtransaction facility - Mailing list pgsql-patches

From Alvaro Herrera
Subject Re: Basic subtransaction facility
Date
Msg-id 20040420053255.GA22859@dcc.uchile.cl
Whole thread Raw
In response to Re: Basic subtransaction facility  (Alvaro Herrera <alvherre@dcc.uchile.cl>)
Responses Re: Basic subtransaction facility
Re: Basic subtransaction facility
List pgsql-patches
On Mon, Apr 19, 2004 at 11:13:35AM -0400, Alvaro Herrera wrote:

> I noticed that I sent an old version because of a system crash (the
> *one* time I don't review vi -r differences it bites me ... argh).  It
> has several obvious mistakes.  Please do not waste your time reviewing
> that; I'll submit a corrected version later, which will also contain
> some more changes.

Ok, hopefully this one is better.

I'm thinking that I'll to add a new elog level to signal a can't-happen
condition within the transaction machinery, which would abort the whole
transaction tree (more than ERROR) but would not take the whole backend
down (less than FATAL).  What should it be called?  Do people agree that
it's needed?

--
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"Et put se mouve" (Galileo Galilei)

Attachment

pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: [JDBC] EXECUTE command tag returns actual command
Next
From: Fabien COELHO
Date:
Subject: Re: pg_restore ignore error patch