From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Incorrect START TRANSACTION implementation |
Date: | 2004-01-27 17:16:47 |
Message-ID: | 200401271816.47493.peter_e@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
SQL99 part 2 clause 16.1 contains this note:
NOTE 327 - The characteristics of a transaction begun by a
<start transaction statement> are as specified in these General
Rules regardless of the characteristics specified by any
preceding <set transaction statement>. That is, even if one
or more characteristics are omitted by the <start transaction
statement>, the defaults specified in the Syntax Rules of this
Subclause are effective and are not affected by any (preceding)
<set transaction statement>.
In other words, this should work:
peter=# set session characteristics as transaction read only;
SET
peter=# start transaction;
START TRANSACTION
peter=# create table test (a int);
ERROR: transaction is read-only
because the default of a bare "start transaction" is read write. I
propose that we change this to follow the standard and keep the
traditional behavior for BEGIN only.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-01-27 17:27:31 | Re: Recursive optimization of IN subqueries |
Previous Message | ohp | 2004-01-27 17:11:20 | Re: Most urgent |