| From: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: WIP: BRIN multi-range indexes |
| Date: | 2021-03-26 14:04:45 |
| Message-ID: | c8cee470-b685-cbb1-1eee-005a7aae6349@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/26/21 2:55 PM, Tom Lane wrote:
> Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> writes:
>> I recall seeing "bus error" on sparc with other patches because of
>> alignment issues, so I wonder if this is what's happening here.
>
> Try compiling with the address sanitizer enabled. Per c.h,
>
> * Testing can be done with "-fsanitize=alignment -fsanitize-trap=alignment"
> * on clang, or "-fsanitize=alignment -fno-sanitize-recover=alignment" on gcc.
>
Bingo! I see the one failing x86_64 machine has -fsanitize=alignment.
thanks
--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Steele | 2021-03-26 14:19:04 | Re: invalid data in file backup_label problem on windows |
| Previous Message | Tom Lane | 2021-03-26 13:55:38 | Re: WIP: BRIN multi-range indexes |