From: | Christoph Berg <myon(at)debian(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: gs_group_1 crashing on 13beta2/s390x |
Date: | 2020-07-16 09:33:58 |
Message-ID: | 20200716093358.GC3534683@msg.df7cb.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Re: Tom Lane
> Given the apparently-can't-happen situation at the call site,
> and the fact that we're not seeing similar failures reported
> elsewhere (and note that every line shown above is at least
> five years old), I'm kind of forced to the conclusion that this
> is a compiler bug. Does adjusting the -O level make it go away?
The problem is that a manual build doesn't crash, and I'm somewhat
reluctant to do a full new package upload (which will keep buildds for
all architectures busy) just for a -O0 test unless we are sure it
helps.
I'd rather play more with the manual build artifacts (which should be
using the same compiler and everything), if anyone has ideas what I
should be trying.
Christoph
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2020-07-16 09:38:03 | Re: problem with RETURNING and update row movement |
Previous Message | Amit Kapila | 2020-07-16 09:32:17 | Re: Which SET TYPE don't actually require a rewrite |