| From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Rahila Syed <rahilasyed90(at)gmail(dot)com>, Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Surprising behaviour of \set AUTOCOMMIT ON |
| Date: | 2016-09-02 08:13:18 |
| Message-ID: | 36ccfa8d-0f00-6acf-e7b4-6a14bc0bb281@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
Some minor comments.
+ <note>
+ <para>
+ Autocommit cannot be set on inside a transaction, the ongoing
+ transaction has to be ended by entering <command>COMMIT</> or
+ <command>ROLLBACK</> before setting autocommit on.
+ </para>
+ </note>
I guess: "cannot be set *to* on" and likewise for "setting autocommit on"
The error message further in the patch spells it correctly:
+ psql_error("\\%s: Cannot set %s to %s inside a transaction, ...
Also (maybe): s/Autocommit/AUTOCOMMIT/g
Thanks,
Amit
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-09-02 08:31:32 | Re: Implement targetlist SRFs using ROWS FROM() (was Changed SRF in targetlist handling) |
| Previous Message | Craig Ringer | 2016-09-02 07:58:33 | Re: Logical decoding slots can go backwards when used from SQL, docs are wrong |