Re: Crash in BRIN minmax-multi indexes

Tomas Vondra <tomas.vondra@enterprisedb.com>

From: Tomas Vondra <tomas.vondra@enterprisedb.com>

To: Justin Pryzby <pryzby@telsasoft.com>

Cc: Jaime Casanova <jcasanov@systemguards.com.ec>, Zhihong Yu <zyu@yugabyte.com>, pgsql-hackers@lists.postgresql.org

Date: 2022-12-30T19:53:50Z

Lists: pgsql-hackers

I finally pushed this fix.

In the end I both relaxed the assert a little bit to allow calling
build_distances for a single range, and added a bail out so that the
caller gets regular NULL and not whatever palloc(0) produces.

Thanks again for the report!


regards

-- 
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Commits

Fix assert in BRIN build_distances
- 02699bc1fd3b 16.0 landed
- c4f64cfab9fe 15.2 landed
- 883dc0214a64 14.7 landed
Fix bug in brin_minmax_multi_union
- d9c5b9a9eeb9 14.0 landed
Fix order of parameters in BRIN minmax-multi calls
- 1dad2a5ea3d1 14.0 landed
Fix BRIN minmax-multi distance for inet type
- e1fbe1181c86 14.0 landed
Fix BRIN minmax-multi distance for timetz type
- 7262f2421a1e 14.0 landed
Fix BRIN minmax-multi distance for interval type
- 2b10e0e3c2ca 14.0 landed