Re: Non-decimal integer literals

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, John Naylor <john(dot)naylor(at)enterprisedb(dot)com>
Subject: Re: Non-decimal integer literals
Date: 2022-01-26 15:10:39
Message-ID: 97aa22d7-b80f-efa1-f368-3dbf73a15980@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 26.01.22 01:02, Tom Lane wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Tue, Jan 25, 2022 at 5:34 AM Peter Eisentraut
>> <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
>>> Which part exactly? There are several different changes proposed here.
>
>> I was just going based on the description of the feature in your
>> original post. If someone is hoping that int4in() will accept only
>> ^\d+$ then they will be disappointed by this patch.
>
> Maybe I misunderstood, but I thought this was about what you could
> write as a SQL literal, not about the I/O behavior of the integer
> types. I'd be -0.1 on changing the latter.

I think it would be strange if I/O routines would accept a different
syntax from the literals. Also, the behavior of a cast from string/text
to a numeric type is usually defined in terms of what the literal syntax
is, so they need to be aligned.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Dilger 2022-01-26 15:24:31 Re: Granting SET and ALTER SYSTE privileges for GUCs
Previous Message Andrew Dunstan 2022-01-26 14:49:10 Re: JSONB docs patch