Re: BUG #18585: Date/time conversion functions are not protected against integer overflow - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #18585: Date/time conversion functions are not protected against integer overflow
Date
Msg-id 964774.1723913132@sss.pgh.pa.us
Whole thread Raw
In response to BUG #18585: Date/time conversion functions are not protected against integer overflow  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #18585: Date/time conversion functions are not protected against integer overflow
List pgsql-bugs
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



pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: BUG #18584: Triggers are not fired or executing when any DML transaction runs
Next
From: Tom Lane
Date:
Subject: Re: BUG #18336: Inconsistency in PostgreSQL 16 Documentation for SHOW Command