Re: Silent overflow of interval type

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Nick Babadzhanian <pgnickb(at)gmail(dot)com>
Cc: Andrey Borodin <amborodin86(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Silent overflow of interval type
Date: 2023-02-20 22:30:56
Message-ID: 3845154.1676932256@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Nick Babadzhanian <pgnickb(at)gmail(dot)com> writes:
> Please find attached the v2 of the said patch with the tests added.

Pushed with light editing (for instance, I don't think interval.sql
is the place to test timestamp operators, even if the result is an
interval).

> I don't know how the decision on
> backpatching is made and whether it makes sense here or not.

We haven't got a really hard policy on that, but in this case
I elected not to, because it didn't seem worth the effort.
It seems fairly unlikely that people would hit this in production.
Also there's the precedent that related changes weren't backpatched.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2023-02-20 22:35:36 Re: [PoC] Federated Authn/z with OAUTHBEARER
Previous Message Joel Jacobson 2023-02-20 22:16:54 Re: Missing free_var() at end of accum_sum_final()?