Re: BUG #16122: segfault pg_detoast_datum (datum=0x0) at fmgr.c:1833numrange query - Mailing list pgsql-bugs

From Adam Scott
Subject Re: BUG #16122: segfault pg_detoast_datum (datum=0x0) at fmgr.c:1833numrange query
Date
Msg-id CA+s62-Mnj-x8_ZXh7tBVU3WJ3cKUsUL2HAp2YaJSXQPw1iypFw@mail.gmail.com
Whole thread Raw
In response to Re: BUG #16122: segfault pg_detoast_datum (datum=0x0) at fmgr.c:1833numrange query  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
Responses Re: BUG #16122: segfault pg_detoast_datum (datum=0x0) at fmgr.c:1833numrange query
List pgsql-bugs
Hi Tomas, thank you for your help!  @Michael it looks like 15 repeats is not enough to say it is "reliably" reproduced: hope this does it.

To reproduce, be sure to start postgres from scratch.   Load the dump file (below).  And then run the following to reliably reproduce the error:
select id from natica_hdu_test
WHERE
"dec_range" <@ '[88.9999998611111,90.0000001388889)';

It was bugging out with an empty table but it seems intermittent. A successful query followed by the one above will not fail sometimes; hence the need for a from-scratch startup instance of postgres.



pgsql-bugs by date:

Previous
From: Adam Scott
Date:
Subject: Re: BUG #16122: segfault pg_detoast_datum (datum=0x0) at fmgr.c:1833numrange query
Next
From: John Thomas
Date:
Subject: gdal30-libs.x86_64 update requires the unavailable libpoppler.so.78