Subject: Re: WIP: BRIN multi-range indexes
From: Tomas Vondra <tomas.vondra@enterprisedb.com>
To: John Naylor <john.naylor@enterprisedb.com>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>,
 PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
References: <20210303001725.GA1766@alvherre.pgsql>
 <23a0a854-8f1a-e965-7121-f76b1b2fc271@enterprisedb.com>
 <cf8fca26-0fdd-ac74-5dac-66a2ccb59f56@enterprisedb.com>
 <8e319879-32ff-1eb8-d7d3-6a3ac8a51728@enterprisedb.com>
 <CAFBsxsHrqP+OMp5cV6yiEzkwobtAp4rnxOGsfm_s_vX8qSNQeQ@mail.gmail.com>
 <35e866e9-d820-07de-b2be-69d5ac479179@enterprisedb.com>
 <71dfd257-c5ce-530d-90d3-7c744a28e97b@enterprisedb.com>
 <CAFBsxsHswPBXQvvW87uSR59MkPNhEB5Txe4sFjVBfE9TR4jrGw@mail.gmail.com>
 <ea369ea5-0d61-bbee-c1c7-bfe17728bab1@enterprisedb.com>
 <54b47e66-bd8a-d44a-2090-fd4b2f49abe6@enterprisedb.com>
 <357fb6d7-649f-822e-ff43-16b39aed68ee@enterprisedb.com>
 <1da94012-f512-ffc8-dd5e-888d862b662e@enterprisedb.com>
Message-ID: <d67e33fe-2a7f-d72d-4f1a-10cef91a5f82@enterprisedb.com>
Date: Fri, 26 Mar 2021 14:38:50 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.8.1
MIME-Version: 1.0
In-Reply-To: <1da94012-f512-ffc8-dd5e-888d862b662e@enterprisedb.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/d67e33fe-2a7f-d72d-4f1a-10cef91a5f82%40enterprisedb.com>
Precedence: bulk


On 3/26/21 2:08 PM, Tomas Vondra wrote:
> Hi,
> 
> I've pushed both the bloom and minmax-multi indexes today.
> 

Hmmm, I see a couple buildfarm animals are upset about the minmax-multi
patch. It does pass for me both on x86_64 and 32-bit ARM (rpi4), so I'm
unable to reproduce this. But most of the machines having issues seem to
be sparc variants, and snapper does this:


[New LWP 1471]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/sparc-linux-gnu/libthread_db.so.1".
Core was generated by `postgres: parallel worker for PID 1350
                             '.
Program terminated with signal 10, Bus error.
#0  0x007167fc in int82gt (fcinfo=0xffcc66d0) at int8.c:399
399		int64		val1 = PG_GETARG_INT64(0);
#0  0x007167fc in int82gt (fcinfo=0xffcc66d0) at int8.c:399
#1  0x00887a94 in FunctionCall2Coll (flinfo=0xb81a2c, collation=0,
arg1=12242916, arg2=0) at fmgr.c:1163


I recall seeing "bus error" on sparc with other patches because of
alignment issues, so I wonder if this is what's happening here.


regards

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