Re: Non-decimal integer literals

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: John Naylor <john(dot)naylor(at)enterprisedb(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Non-decimal integer literals
Date: 2022-11-15 10:31:03
Message-ID: b70b15fc-7f8d-5370-21fc-4ec3c154aef3@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 14.11.22 08:25, John Naylor wrote:
> Regarding the patch, it looks good overall. My only suggestion would be
> to add a regression test for just below and just above overflow, at
> least for int2.

ok

> Minor nits:
>
> - * Process {integer}.  Note this will also do the right thing with
> {decimal},
> + * Process {*integer}.  Note this will also do the right thing with
> {numeric},
>
> I scratched my head for a while, thinking this was Flex syntax, until I
> realized my brain was supposed to do shell-globbing first, at which
> point I could see it was referring to multiple Flex rules. I'd try to
> rephrase.

ok

> +T661 Non-decimal integer literals YES SQL:202x draft
>
> Is there an ETA yet?

March 2023

> Also, it's not this patch's job to do it, but there are at least a half
> dozen places that open-code turning a hex char into a number. It might
> be a good easy "todo item" to unify that.

right

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2022-11-15 10:36:53 Re: Add palloc_aligned() to allow arbitrary power of 2 memory alignment
Previous Message Peter Eisentraut 2022-11-15 10:18:59 Re: libpq support for NegotiateProtocolVersion