Re: WIP: BRIN multi-range indexes

From: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
To: John Naylor <john(dot)naylor(at)2ndquadrant(dot)com>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: WIP: BRIN multi-range indexes
Date: 2020-09-17 19:19:18
Message-ID: 20200917191918.ezcfekrd25h55lco@development
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers


cfbot was not quite happy with the last version either - there was a bug
in 0003 part, allocating smaller chunk of memory than needed. Attached
is a version fixing that, hopefully cfbot will be happy with this one.


Tomas Vondra
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment Content-Type Size
0001-Pass-all-scan-keys-to-BRIN-consistent-func-20200917b.patch text/plain 23.5 KB
0002-Move-IS-NOT-NULL-handling-from-BRIN-suppor-20200917b.patch text/plain 23.3 KB
0003-optimize-allocations-20200917b.patch text/plain 3.9 KB
0004-BRIN-bloom-indexes-20200917b.patch text/plain 138.7 KB
0005-BRIN-minmax-multi-indexes-20200917b.patch text/plain 217.3 KB
0006-Ignore-correlation-for-new-BRIN-opclasses-20200917b.patch text/plain 4.1 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2020-09-17 20:09:51 Re: Planner, check if can use consider HASH for groupings (src/backend/optimizer/plan/planner.c)
Previous Message Magnus Hagander 2020-09-17 19:17:07 Re: Policy on cross-posting to multiple lists