| From: | "Merlin Moncure" <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | "Merlin Moncure" <mmoncure(at)gmail(dot)com>, "Dawid Kuroczko" <qnex42(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: savepoint improvements |
| Date: | 2007-01-22 19:19:50 |
| Message-ID: | b42b73150701221119m2f139b72i9dbeefb9469fe9cc@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/22/07, Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
> > i think so...Martijn said it best: you can 'rollback' to, but you
> > can't 'commit' to. The 'commit to' would be the arguably much more
> > useful way of disposing of a savepoint. But that should be taken up
> > with sql standards committee :(.
>
> You can RELEASE a savepoint though.
not following an error. RELEASE serves absolutely no purpose
whatsoever. it's like the sql equivalent of an assembly NOP...wasts
cpu cycles for no reason.
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-01-22 19:22:08 | Re: [HACKERS] Win32 WEXITSTATUS too |
| Previous Message | Heikki Linnakangas | 2007-01-22 19:19:02 | Re: [HACKERS] Autovacuum Improvements |