From: Tom Lane <tgl@sss.pgh.pa.us>
To: exclusion@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18585: Date/time conversion functions are not protected
 against integer overflow
In-reply-to: <18585-db646741dd649abd@postgresql.org>
References: <18585-db646741dd649abd@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Sat, 17 Aug 2024 15:00:01 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <964773.1723913132.1@sss.pgh.pa.us>
Date: Sat, 17 Aug 2024 12:45:32 -0400
Message-ID: <964774.1723913132@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/964774.1723913132%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> The date/time conversion functions do_to_timestamp(), DCH_from_char(),
> ... lack reliable checks for integer overflow in the input components.

It's pretty hard to get excited about that, given that the overflow
limits are so many orders of magnitude beyond the useful input range.
There are plenty of garbage-in-garbage-out scenarios associated with
(mis)use of the to_xxx functions, and this feels like just another one.

If anybody does feel excited about the topic, I'm not going to stand
in their way ... but I'm not excited.

			regards, tom lane