Re: Non-decimal integer literals - Mailing list pgsql-hackers

From Christoph Berg
Subject Re: Non-decimal integer literals
Date
Msg-id YgqkV4HOuir1IemY@msg.df7cb.de
Whole thread Raw
In response to Non-decimal integer literals  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
List pgsql-hackers
Re: Peter Eisentraut
> This adds support in the lexer as well as in the integer type input
> functions.
> 
> Those core parts are straightforward enough, but there are a bunch of other
> places where integers are parsed, and one could consider in each case
> whether they should get the same treatment, for example the replication
> syntax lexer, or input function for oid, numeric, and int2vector.

One thing I always found weird is that timeline IDs appear most
prominently as hex numbers in WAL filenames, but they are printed as
decimal in the log ("new timeline id nn"), and have to be specified as
decimal in recovery_target_timeline.

Perhaps both these could make use of 0xhex numbers as well.

Christoph



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: Fix overflow in justify_interval related functions
Next
From: Tom Lane
Date:
Subject: Re: Fix overflow in justify_interval related functions