Re: Nested Transactions, Abort All

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>
Cc: Thomas Swan <tswan(at)idigx(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Nested Transactions, Abort All
Date: 2004-07-02 23:43:47
Message-ID: 3555.1088811827@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> writes:
> You can't have subtransactions inside an implicit transaction block,

It would be folly to design on that assumption. We *will* have that
situation just as soon as plpgsql allows creating subtransactions
(which I trust you'll agree will happen soon). All you have to do
is call such a function from a bare SELECT. I do not think you'll
be able to legislate that people must say BEGIN first.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Oliver Jowett 2004-07-03 00:16:50 Re: [Re] Re: PREPARE and transactions
Previous Message Jeroen T. Vermeulen 2004-07-02 23:33:42 Re: [Re] Re: PREPARE and transactions