Re: [HACKERS] SAVEPOINT syntax again - Mailing list pgsql-patches

From Bruce Momjian
Subject Re: [HACKERS] SAVEPOINT syntax again
Date
Msg-id 200408120326.i7C3QUp13906@candle.pha.pa.us
Whole thread Raw
In response to Re: [HACKERS] SAVEPOINT syntax again  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] SAVEPOINT syntax again  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches
Tom Lane wrote:
> Oliver Jowett <oliver@opencloud.com> writes:
> > Oracle has ROLLBACK TO [ SAVEPOINT ] <savepoint specifier>
> > DB2 has ROLLBACK TO SAVEPOINT <savepoint specifier>
>
> I would go with Oracle's lead here, first because they are the de facto
> standard, and second because I don't want to have to type out SAVEPOINT
> every time I use one of these commands.
>
> > <release savepoint statement> ::= RELEASE SAVEPOINT <savepoint specifier>
>
> > Oracle does not have RELEASE SAVEPOINT.
> > DB2 has RELEASE [ TO ] SAVEPOINT <savepoint specifier>
>
> I'd vote for RELEASE [ SAVEPOINT ] <name> (for brevity, and for
> consistency with ROLLBACK).  I feel no urge to copy DB2.

Are we ever going to use "RELEASE" for prepared statements?  If so
making SAVEPOINT optional might be a bad idea.

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] SAVEPOINT syntax again
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] SAVEPOINT syntax again