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

From PG Bug reporting form
Subject BUG #17819: The assert failed #17334 has not been repaired
Date
Msg-id 17819-1e12c61d0829db39@postgresql.org
Whole thread Raw
Responses Re: BUG #17819: The assert failed #17334 has not been repaired
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      17819
Logged by:          xin wen
Email address:      xinwen@stu.scu.edu.cn
PostgreSQL version: 15.2
Operating system:   Ubuntu 20.04
Description:

The assert failed reported in #17334
(https://www.postgresql.org/message-id/17334-135f485c21739caa%40postgresql.org)
has not been repaired.
When executing the following query:

CREATE TABLE point_tbl(f1 point);
CREATE INDEX gpointind ON point_tbl USING gist(f1);
INSERT INTO point_tbl SELECT ('0,0') FROM generate_series(1, 185);
INSERT INTO point_tbl VALUES ('0,NaN');
SET enable_seqscan=off; SELECT f1 <-> point '(0,0)' AS dist FROM point_tbl
ORDER BY dist;

The FailedAssertion("box->low.y <= box->high.y", File:
"/backend/access/gist/gistproc.c") will still occur.


pgsql-bugs by date:

Previous
From: Richard Guo
Date:
Subject: Re: Clause accidentally pushed down ( Possible bug in Making Vars outer-join aware)
Next
From: PG Bug reporting form
Date:
Subject: BUG #17821: Assertion failed in heap_update() due to heap pruning