Re: Nested transactions: low level stuff - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Nested transactions: low level stuff
Date
Msg-id 18473.1048127901@sss.pgh.pa.us
Whole thread Raw
In response to Re: Nested transactions: low level stuff  (Hiroshi Inoue <Inoue@tpf.co.jp>)
Responses Re: Nested transactions: low level stuff  (Alvaro Herrera <alvherre@dcc.uchile.cl>)
List pgsql-hackers
Hiroshi Inoue <Inoue@tpf.co.jp> writes:
> Sorry I have a basic question.
> Was there any consensus we would introduce nested transactions
> (or savepoints) in the way currently discussed ?

I think we are a long way from saying we can or will actually do it.
Error handling and resource management (eg locks) are a couple of other
huge cans of worms that have yet to be opened.  But certainly a solid
design for the transaction logging and tuple validity checking is a
necessary step.

My feeling is that the right way to proceed is to nail down a paper
design for each of the major aspects of the problem, before anyone
actually spends any time coding.  There would be little point in
implementing subtransaction logging if we don't know how to do the
other things.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: A bad behavior under autocommit off mode
Next
From: Bruce Momjian
Date:
Subject: Re: Open 7.4 features