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

From: Adam Scott <adam(dot)c(dot)scott(at)gmail(dot)com>
To: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16122: segfault pg_detoast_datum (datum=0x0) at fmgr.c:1833 numrange query
Date: 2019-11-18 23:59:14
Message-ID: CA+s62-Mnj-x8_ZXh7tBVU3WJ3cKUsUL2HAp2YaJSXQPw1iypFw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

Here is the backup file ~3.5 MB:
https://drive.google.com/open?id=1cMc8pMT_aDAW7miplbrpDDcn-JZ0td8M

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message John Thomas 2019-11-19 00:45:13 gdal30-libs.x86_64 update requires the unavailable libpoppler.so.78
Previous Message Adam Scott 2019-11-18 22:51:25 Re: BUG #16122: segfault pg_detoast_datum (datum=0x0) at fmgr.c:1833 numrange query