| From: | Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Etsuro Fujita <efujita(at)postgresql(dot)org>, pgsql-committers <pgsql-committers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pgsql: Fix some issues with step generation in partition pruning. |
| Date: | 2020-08-02 03:01:51 |
| Message-ID: | CAPmGK16gDf0jGkiT-XoYp7PWuMfOjbXFuvzMZC3uieBteqxSCQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
On Sun, Aug 2, 2020 at 3:16 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I've concluded that this is probably a compiler bug. It doesn't fail
> at optimization level -O0 or -O2, only -O1; and trying to step through
> gen_partprune_steps_internal() suggests that the part_scheme local
> variable is changing value, which it surely should not. Since gaur
> is running an ancient gcc version, and -O1 is doubtless a pretty
> under-tested optimization level, bugs there are not so surprising.
>
> There wasn't any amazingly good reason to be using -O1 for gaur,
> so I've switched the animal to use -O2. I expect it'll go back
> to green in a few hours.
I checked that gaur got back to green. Thanks!
Best regards,
Etsuro Fujita
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-08-02 15:00:21 | pgsql: Adjust pgcrypto's expected test results for --disable-strong-ran |
| Previous Message | David Rowley | 2020-08-02 02:25:07 | pgsql: Use int64 instead of long in incremental sort code |