| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Oliver Jowett <oliver(at)opencloud(dot)com> |
| Cc: | Patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] SAVEPOINT syntax again |
| Date: | 2004-08-12 02:56:22 |
| Message-ID: | 23439.1092279382@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Fuhr | 2004-08-12 02:56:27 | 8.0.0beta1: Ownership of implicit sequences after dump/restore |
| Previous Message | Philip Warner | 2004-08-12 02:56:16 | Re: pg_restore (libpq? parser?) bug in 8 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-08-12 03:26:30 | Re: [HACKERS] SAVEPOINT syntax again |
| Previous Message | Tom Lane | 2004-08-12 02:23:50 | Re: pg_dump 'die_on_errors' |