Re: BUG #19887: cube expression index returns wrong rows after extra_float_digits change

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: idrissaajalloh(at)gmail(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19887: cube expression index returns wrong rows after extra_float_digits change
Date: 2026-11-12 18:15:11
Message-ID: 49108.1794507311@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> A cube expression index built with extra_float_digits = 0 returns no rows
> after the setting is changed to 3, while sequential evaluation of the same
> predicate returns one row. cube_out(cube) is marked IMMUTABLE, but the same
> cube value is rendered as (1.23456789012346) with the first setting and
> (1.2345678901234567) with the second.

Yeah. There's a wider discussion in progress about this class of
bugs, over here:

https://www.postgresql.org/message-id/flat/19644-d6db3fb5e5ad92f4%40postgresql.org

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Сергей Шиндерук 2026-11-12 18:18:35 Re: BUG #19894: CREATE DATABASE logs all-zeros visibility map
Previous Message Christophe Pettus 2026-11-12 17:40:30 Re: BUG #19894: CREATE DATABASE logs all-zeros visibility map