From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
Cc: | Zhihong Yu <zyu(at)yugabyte(dot)com>, Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Crash in BRIN minmax-multi indexes |
Date: | 2021-04-01 02:56:43 |
Message-ID: | CA+hUKGKM5cLP0PNBCz_J1btffxX8MKKSmc_DB-WEii_XdadDvw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Apr 1, 2021 at 11:25 AM Tomas Vondra
<tomas(dot)vondra(at)enterprisedb(dot)com> wrote:
> As for why the regression tests did not catch this, it's most likely
> because the data is likely generated in "nice" ordering, or something
> like that. I'll see if I can tweak the ordering to trigger these issues
> reliably, and I'll do a bit more randomized testing.
For what little it's worth now that you've cracked it, I can report
that make check blows up somewhere in here on a 32 bit system with
--with-blocksize=32 :-)
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2021-04-01 02:59:15 | Improve error matching patterns in the SSL tests |
Previous Message | Masahiko Sawada | 2021-04-01 02:33:54 | Re: Flaky vacuum truncate test in reloptions.sql |