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

From Daniel Verite
Subject Re: Surprising behaviour of \set AUTOCOMMIT ON
Date
Msg-id 793934fa-62c4-42b7-878b-f93205d58722@mm
Whole thread Raw
In response to Re: Surprising behaviour of \set AUTOCOMMIT ON  (Rahila Syed <rahilasyed90@gmail.com>)
List pgsql-hackers
    Rahila Syed wrote:

> >Above error coming because in below code block change, you don't have
> check for
> >command (you should check opt0 for AUTOCOMMIT command)

> Corrected in the attached.

There are other values than ON: true/yes and theirs abbreviations,
the value 1, and anything that doesn't resolve to OFF is taken as ON.
ParseVariableBool() in commands.c already does the job of converting
these to bool, the new code should probably just call that function
instead of parsing the value itself.

Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite



pgsql-hackers by date:

Previous
From: Petr Jelinek
Date:
Subject: Re: Logical Replication WIP
Next
From: "Daniel Verite"
Date:
Subject: Re: Surprising behaviour of \set AUTOCOMMIT ON