Re: Surprising behaviour of \set AUTOCOMMIT ON

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Daniel Verite" <daniel(at)manitou-mail(dot)org>
Cc: "Rushabh Lathia" <rushabh(dot)lathia(at)gmail(dot)com>, "Rahila Syed" <rahilasyed90(at)gmail(dot)com>, "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-03 16:05:38
Message-ID: 10040.1472918738@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Daniel Verite" <daniel(at)manitou-mail(dot)org> writes:
> Rushabh Lathia wrote:
>> so its good to have all the set variable related checks inside
>> SetVariable().

> There's already another way to skip the \set check:
> select 'on' as "AUTOCOMMIT" \gset

Hmm, that might be a bug.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Vladimir Sitnikov 2016-09-03 16:31:13 Re: Index Onlys Scan for expressions
Previous Message Tom Lane 2016-09-03 16:04:03 Re: Logical Replication WIP