Re: pgsql: Fix some issues with step generation in partition pruning. - Mailing list pgsql-committers

From Etsuro Fujita
Subject Re: pgsql: Fix some issues with step generation in partition pruning.
Date
Msg-id CAPmGK16gDf0jGkiT-XoYp7PWuMfOjbXFuvzMZC3uieBteqxSCQ@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Fix some issues with step generation in partition pruning.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
On Sun, Aug 2, 2020 at 3:16 AM Tom Lane <tgl@sss.pgh.pa.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



pgsql-committers by date:

Previous
From: David Rowley
Date:
Subject: pgsql: Use int64 instead of long in incremental sort code
Next
From: Tom Lane
Date:
Subject: pgsql: Adjust pgcrypto's expected test results for --disable-strong-ran