On Tue, Aug 16, 2016 at 5:25 PM, Rahila Syed <rahilasye...@gmail.com> wrote: >>I think I like the option of having psql issue an error. On the >>server side, the transaction would still be open, but the user would >>receive a psql error message and the autocommit setting would not be >>changed. So the user could type COMMIT or ROLLBACK manually and then >>retry changing the value of the setting. > > Throwing psql error comes out to be most accepted outcome on this thread. I > agree it is safer than guessing user intention. > > Although according to the default behaviour of psql, error will abort the > current transaction and roll back all the previous commands.
A server error would do that, but a psql errror won't. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers