pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #18835: spgist index fails to accept point with NaN
2+ messages / 2 participants
[nested] [flat]
* BUG #18835: spgist index fails to accept point with NaN
@ 2025-03-07 18:00 PG Bug reporting form <noreply@postgresql.org>
2025-03-07 20:08 ` Re: BUG #18835: spgist index fails to accept point with NaN Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 2+ messages in thread
From: PG Bug reporting form @ 2025-03-07 18:00 UTC (permalink / raw)
To: pgsql-bugs@lists.postgresql.org; +Cc: exclusion@gmail.com
The following bug has been logged on the website:
Bug reference: 18835
Logged by: Alexander Lakhin
Email address: exclusion@gmail.com
PostgreSQL version: 17.4
Operating system: Ubuntu 24.04
Description:
The following script:
CREATE TABLE t(p point);
INSERT INTO t SELECT point(g, g) FROM generate_series(1, 1000) g;
INSERT INTO t VALUES ('(0,NaN)'::point);
CREATE INDEX spgist_idx ON t USING spgist(p);
triggers:
ERROR: XX000: getQuadrant: impossible case
LOCATION: getQuadrant, spgquadtreeproc.c:77
Reproduced starting from 8daeb5ddd.
This anomaly is discovered with SQLsmith.
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: BUG #18835: spgist index fails to accept point with NaN
2025-03-07 18:00 BUG #18835: spgist index fails to accept point with NaN PG Bug reporting form <noreply@postgresql.org>
@ 2025-03-07 20:08 ` Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 2+ messages in thread
From: Tom Lane @ 2025-03-07 20:08 UTC (permalink / raw)
To: exclusion@gmail.com; +Cc: pgsql-bugs@lists.postgresql.org
PG Bug reporting form <noreply@postgresql.org> writes:
> The following script:
> CREATE TABLE t(p point);
> INSERT INTO t SELECT point(g, g) FROM generate_series(1, 1000) g;
> INSERT INTO t VALUES ('(0,NaN)'::point);
> CREATE INDEX spgist_idx ON t USING spgist(p);
> triggers:
> ERROR: XX000: getQuadrant: impossible case
Yeah. There's been some past attempts to clean up our behavior
for NaNs in geometric values, but it's such a mess that not
much progress has been made. So I can't get excited about
worrying about this case in particular (especially since I don't
see any easy fix). I wonder if we shouldn't just ban NaNs in
the geometric types.
regards, tom lane
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2025-03-07 20:08 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-03-07 18:00 BUG #18835: spgist index fails to accept point with NaN PG Bug reporting form <noreply@postgresql.org>
2025-03-07 20:08 ` Tom Lane <tgl@sss.pgh.pa.us>
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