Re: Bus error in pg_logical_slot_get_changes (9.4.7, sparc)

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Christoph Berg <christoph(dot)berg(at)credativ(dot)de>, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Bus error in pg_logical_slot_get_changes (9.4.7, sparc)
Date: 2016-04-13 17:58:27
Message-ID: 20160413175827.dmlbtdf7c3mgmnex@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2016-04-13 13:54:10 -0400, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > On 2016-04-13 11:41:17 +0200, Christoph Berg wrote:
> >> I've just uploaded 9.4.7 for Debian's wheezy-backports suite.
> >> Unfortunately it's now crashing twice in the contrib/test_decoding
> >> regression tests on sparc. I could reproduce the error on the porter
> >> box:
>
> > Hrmpf, I guess this is an alignment issue.
>
> Maybe, but then why didn't the buildfarm detect it? We certainly
> have several critters that would be sticky about this.

I'm wondering the same. My theory is that it might only actually matter
when built optimized; which few animals do. The instruction selection
definitely can influence whether an alignment issue becomes aparent or
not. Unless that idea pans out I guess I'll have to go through the
motions to get access to that porter box. I had that at some point in
the past (debugging something turning out to be a compiler bug).

Andres

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Christoph Berg 2016-04-13 21:11:52 Re: Bus error in pg_logical_slot_get_changes (9.4.7, sparc)
Previous Message Tom Lane 2016-04-13 17:54:10 Re: Bus error in pg_logical_slot_get_changes (9.4.7, sparc)