From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Oliver Jowett <oliver(at)opencloud(dot)com>, Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] SAVEPOINT syntax again |
Date: | 2004-08-12 03:26:30 |
Message-ID: | 200408120326.i7C3QUp13906@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Tom Lane wrote:
> Oliver Jowett <oliver(at)opencloud(dot)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(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-08-12 03:27:14 | Re: pg_dump 'die_on_errors' |
Previous Message | Tom Lane | 2004-08-12 03:25:57 | Re: pg_restore (libpq? parser?) bug in 8 |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-08-12 03:27:14 | Re: pg_dump 'die_on_errors' |
Previous Message | Tom Lane | 2004-08-12 02:56:22 | Re: [HACKERS] SAVEPOINT syntax again |