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

From Robert Haas
Subject Re: Surprising behaviour of \set AUTOCOMMIT ON
Date
Msg-id CA+TgmoYFtGQwP_7bMi6DJyoqSV4Vh3wnCpMsViYUVOOfmU4d2g@mail.gmail.com
Whole thread Raw
In response to Re: Surprising behaviour of \set AUTOCOMMIT ON  (Rahila Syed <rahilasyed90@gmail.com>)
Responses Re: Surprising behaviour of \set AUTOCOMMIT ON
List pgsql-hackers
On Thu, Sep 15, 2016 at 7:29 AM, Rahila Syed <rahilasyed90@gmail.com> wrote:
> In keeping with current design of hooks instead of rejecting autocommit 'ON'
> setting inside
> a transaction,the value can be set to 'ON' with a psql_error displaying that
> the value
> will be effective when the current transaction has ended.

Hmm, that seems like a reasonable compromise.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: select_parallel test fails with nonstandard block size
Next
From: Anastasia Lubennikova
Date:
Subject: File system operations.