Re: Surprising behaviour of \set AUTOCOMMIT ON - Mailing list pgsql-hackers

From Amit Langote
Subject Re: Surprising behaviour of \set AUTOCOMMIT ON
Date
Msg-id 36ccfa8d-0f00-6acf-e7b4-6a14bc0bb281@lab.ntt.co.jp
Whole thread Raw
In response to Re: Surprising behaviour of \set AUTOCOMMIT ON  (Rahila Syed <rahilasyed90@gmail.com>)
List 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





pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: Logical decoding slots can go backwards when used from SQL, docs are wrong
Next
From: Robert Haas
Date:
Subject: Re: Implement targetlist SRFs using ROWS FROM() (was Changed SRF in targetlist handling)