Re: BUG #17819: The assert failed #17334 has not been repaired - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #17819: The assert failed #17334 has not been repaired
Date
Msg-id 1908490.1677773340@sss.pgh.pa.us
Whole thread Raw
In response to BUG #17819: The assert failed #17334 has not been repaired  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
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.gmail.com



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #17818: CTE is not returning the right data.
Next
From: Alvaro Herrera
Date:
Subject: Re: BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails