Re: Crash in BRIN minmax-multi indexes

From: Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>
To: Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>
Cc: Zhihong Yu <zyu(at)yugabyte(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Crash in BRIN minmax-multi indexes
Date: 2021-04-04 18:01:52
Message-ID: b0e6d18c-9cd4-6639-271e-71c211b32ed8@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

BTW, for the inet data type, I considered simply calling the "minus"
function, but that does not work because of this strange behavior:

int4=# select '10.1.1.102/32'::inet > '10.1.1.142/24'::inet;
?column?
----------
t
(1 row)

int4=# select '10.1.1.102/32'::inet - '10.1.1.142/24'::inet;
?column?
----------
-40
(1 row)

That is, (a>b) but then (a-b) < 0. AFAICS it's due to comparator
considering the mask, while the minus ignores it. I find it a bit
strange, but I assume it's intentional.

regards

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Anton Voloshin 2021-04-04 18:09:33 Re: possible repalloc() in icu_convert_case()
Previous Message Tomas Vondra 2021-04-04 17:52:50 Re: Crash in BRIN minmax-multi indexes