Hi,
Thanks for the analysis. I was able to reproduce the issue.
On Thu, Oct 15, 2026 at 9:03 PM PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
>
> btree_ts.c avoids this. gbt_ts_penalty does its own double arithmetic on the
> raw int64 values, gbt_ts_dist returns get_float8_infinity() for non-finite
> input, and ts_dist/tstz_dist return a saturated interval.
>
I'm attaching a patch which uses the same logic as btree_ts.c and
btree_int.c in btree_date.co to handle these issues. Please take a
look.
Thanks & Regards
Nitin Motiani,
Google