From: Tom Lane <tgl@sss.pgh.pa.us>
To: exclusion@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18835: spgist index fails to accept point with NaN
In-reply-to: <18835-deaf2add28625ed3@postgresql.org>
References: <18835-deaf2add28625ed3@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Fri, 07 Mar 2025 18:00:01 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1122077.1741378100.1@sss.pgh.pa.us>
Date: Fri, 07 Mar 2025 15:08:20 -0500
Message-ID: <1122078.1741378100@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1122078.1741378100%40sss.pgh.pa.us>
Precedence: bulk

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