Re: Parsing bool type value - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Parsing bool type value
Date
Msg-id CAA4eK1K=jLmN8j13HVQ9ppewL7+rGMs=-2mX99UAyuYoP2DOXA@mail.gmail.com
Whole thread Raw
In response to Parsing bool type value  (Sawada Masahiko <sawada.mshk@gmail.com>)
Responses Re: Parsing bool type value  (Sawada Masahiko <sawada.mshk@gmail.com>)
List pgsql-hackers
On Tue, Aug 20, 2013 at 1:11 PM, Sawada Masahiko <sawada.mshk@gmail.com> wrote:
> Hi all,
>
> Taking a look at PostgreSQL HEAD today, I noticed that currently
> PostgreSQL allows "of" value as bool type value.
> So user can execute the following SQL.
>
> =# SET enbale_seqscan TO of;
>
> And I read the source code related to parsing bool value.
> It compare TWO characters "off" and the setting value in
> parse_bool_with_len() function.
> Should we deny the "of" value as bool type value?
When I checked the manual for values of bool types, it says as follows: " Boolean values can be written as on, off,
true,false, yes, no, 1,
 
0 (all case-insensitive) or any unambiguous prefix of these."  Now "of" can be considered as unambiguous prefix of
"off",so it
 
might be intentional.  Please refer below link for more detailed description:
http://www.postgresql.org/docs/devel/static/config-setting.html#CONFIG-SETTING-NAMES-VALUES



With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Karol Trzcionka
Date:
Subject: Re: GSOC13 proposal - extend RETURNING syntax
Next
From: Alvaro Herrera
Date:
Subject: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])