Re: Crash in BRIN minmax-multi indexes - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Crash in BRIN minmax-multi indexes
Date
Msg-id CA+hUKGKM5cLP0PNBCz_J1btffxX8MKKSmc_DB-WEii_XdadDvw@mail.gmail.com
Whole thread Raw
In response to Re: Crash in BRIN minmax-multi indexes  (Tomas Vondra <tomas.vondra@enterprisedb.com>)
List pgsql-hackers
On Thu, Apr 1, 2021 at 11:25 AM Tomas Vondra
<tomas.vondra@enterprisedb.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 :-)



pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: Flaky vacuum truncate test in reloptions.sql
Next
From: Michael Paquier
Date:
Subject: Improve error matching patterns in the SSL tests