Re: savepoint improvements - Mailing list pgsql-hackers

From Tom Lane
Subject Re: savepoint improvements
Date
Msg-id 9250.1169267591@sss.pgh.pa.us
Whole thread Raw
In response to savepoint improvements  ("Merlin Moncure" <mmoncure@gmail.com>)
Responses Re: savepoint improvements  ("Merlin Moncure" <mmoncure@gmail.com>)
List pgsql-hackers
"Merlin Moncure" <mmoncure@gmail.com> writes:
> I suspect the savepoint command is almost never used
> outside of oracle compatibility efforts.

Last I heard, we implemented it because it is in the SQL standard.
I have no idea (nor do I much care) whether it's oracle-compatible.

> BEGIN;
> SAVEPOINT X;
> COMMIT ON ERRORS SELECT FOO();

> --or--

> BEGIN;
> SAVEPOINT x;
> SAVEPOINT y ON ERRORS SELECT FOO; -- (or ROLLBACK TO SAVEPOINT x);
> COMMIT;

> comments? fast track to todo list? :-)

Not exactly.  You haven't even made clear what you think that means,
let alone how it would be implemented.  What context is foo() supposed
to be executed in?  What happens if it fails?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Fix for bug in plpython bool type conversion
Next
From: Tom Lane
Date:
Subject: Re: Planning aggregates which require sorted or distinct