From: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "'pgsql-hackers'" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: A bad behavior under autocommit off mode |
Date: | 2003-02-21 00:12:36 |
Message-ID: | 3E556EF4.244FB87F@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
>
> "Hiroshi Inoue" <inoue(at)tpf(dot)co(dot)jp> writes:
> > The simplest way seems to accept COMMIT any time under autocommit
> > off mode.
>
> That's just hiding the most visible symptom. The real problem here is
> that the SELECT is already committed, when it shouldn't be.
The warning means that the transaction is not yet begun
before the chained query is issued. The check seems originally
for COMMIT without BEGIN under autocommit on mode. It also
cancels a transaction for the query '..;..;commit;..' under
autocommit on mode. It's also bad because it only reports a
warning. Anyway should 'set autocommit to off;commit' cause
a warning or an error in the first place ?
regards,
Hiroshi Inoue
http://www.geocities.jp/inocchichichi/psqlodbc/
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-02-21 00:15:24 | Re: A bad behavior under autocommit off mode |
Previous Message | Josh Berkus | 2003-02-21 00:06:39 | Re: request for sql3 compliance for the update command |