From: Tom Lane <tgl@sss.pgh.pa.us>
To: xinwen@stu.scu.edu.cn
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17819: The assert failed #17334 has not been repaired
Date: Thu, 02 Mar 2023 11:09:00 -0500
Message-ID: <1908490.1677773340@sss.pgh.pa.us> (raw)
In-Reply-To: <17819-1e12c61d0829db39@postgresql.org>
References: <17819-1e12c61d0829db39@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> The assert failed reported in #17334
> (https://www.postgresql.org/message-id/17334-135f485c21739caa%40postgresql.org)
> has not been repaired.
If supporting NaNs in geometric types excites you, then by all means
step up and work on it, but it's not a high-priority thing for most
of us. We've put some effort into the area before (e.g. [1]) but
arriving at self-consistent definitions is hard, and implementing
them is messy, and TBH the geometric types are a development backwater
in the first place.
At this point I'd be about ready to forbid NaNs in geometric types.
But even making that happen is work that nobody's volunteered for.
regards, tom lane
[1] https://www.postgresql.org/message-id/flat/CAGf+fX70rWFOk5cd00uMfa__0yP+vtQg5ck7c2Onb-Yczp0URA@mail....
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-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, xinwen@stu.scu.edu.cn, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17819: The assert failed #17334 has not been repaired
In-Reply-To: <1908490.1677773340@sss.pgh.pa.us>
* 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