pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tomas Vondra <tomas.vondra@postgresql.org>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Fix minmax-multi on infinite date/timestamp values
Date: Fri, 27 Oct 2023 16:59:57 +0000
Message-ID: <E1qwQBg-002dLZ-Nc@gemulon.postgresql.org> (raw)

Fix minmax-multi on infinite date/timestamp values

Make sure that infinite values in date/timestamp columns are treated as
if in infinite distance. Infinite values should not be merged with other
values, leaving them as outliers. The code however returned distance 0
in this case, so that infinite values were merged first. While this does
not break the index (i.e. it still produces correct query results), it
may make it much less efficient.

We don't need explicit handling of infinite date/timestamp values when
calculating distances, because those values are represented as extreme
but regular values (e.g. INT64_MIN/MAX for the timestamp type).

We don't need an exact distance, just a value that is much larger than
distanced between regular values. With the added cast to double values,
we can simply subtract the values.

The regression test queries a value in the "gap" and checks the range
was properly eliminated by the BRIN index.

This only affects minmax-multi indexes on timestamp/date columns with
infinite values, which is not very common in practice. The affected
indexes may need to be rebuilt.

Backpatch to 14, where minmax-multi indexes were introduced.

Reported-by: Ashutosh Bapat
Reviewed-by: Ashutosh Bapat, Dean Rasheed
Backpatch-through: 14
Discussion: https://postgr.es/m/eef0ea8c-4aaa-8d0d-027f-58b1f35dd170@enterprisedb.com

Branch
------
REL_14_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/52c934cc1f2ee947a76dfc395403b07c24bb6712

Modified Files
--------------
src/backend/access/brin/brin_minmax_multi.c |  6 ---
src/test/regress/expected/brin_multi.out    | 57 +++++++++++++++++++++++++++++
src/test/regress/sql/brin_multi.sql         | 39 ++++++++++++++++++++
3 files changed, 96 insertions(+), 6 deletions(-)



view thread (4+ messages)

Message-ID: <E1qwQBg-002dLZ-Nc@gemulon.postgresql.org>
Permalink:  ../E1qwQBg-002dLZ-Nc@gemulon.postgresql.org/
Also on:    postgresql.org/message-id/E1qwQBg-002dLZ-Nc@gemulon.postgresql.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-committers@postgresql.org
  Cc: tomas.vondra@postgresql.org, pgsql-committers@lists.postgresql.org
  Subject: Re: pgsql: Fix minmax-multi on infinite date/timestamp values
  In-Reply-To: <E1qwQBg-002dLZ-Nc@gemulon.postgresql.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox