Re: WIP: BRIN multi-range indexes

From: Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>
To: Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: WIP: BRIN multi-range indexes
Date: 2020-11-08 18:21:51
Message-ID: 09dde3fc-24ac-1874-dd29-d1cba0615446@enterprisedb.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Seems I forgot to replace uint16 with uint32 in couple places when
fixing the one-hash code, so it was triggering SIGFPE because of
division by 0. Here's a fixed patch series.

regards

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

Attachment Content-Type Size
0001-Pass-all-scan-keys-to-BRIN-consistent-funct-20201108.patch text/x-patch 23.5 KB
0002-Move-IS-NOT-NULL-handling-from-BRIN-support-20201108.patch text/x-patch 23.3 KB
0003-Optimize-allocations-in-bringetbitmap-20201108.patch text/x-patch 4.4 KB
0004-BRIN-bloom-indexes-20201108.patch text/x-patch 138.9 KB
0005-use-one-hash-bloom-variant-20201108.patch text/x-patch 8.5 KB
0006-one-hash-tweaks-20201108.patch text/x-patch 3.7 KB
0007-BRIN-minmax-multi-indexes-20201108.patch text/x-patch 217.3 KB
0008-Ignore-correlation-for-new-BRIN-opclasses-20201108.patch text/x-patch 4.2 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2020-11-08 21:53:34 Re: list of extended statistics on psql
Previous Message Tom Lane 2020-11-08 17:46:44 Re: [BUG]: segfault during update