Re: pgsql: Fix some issues with step generation in partition pruning.

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com>, 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-03 14:36:13
Message-ID: CA+TgmoZbMsLOgTTvK8L94C=7k22iopLOQQ0JjBLSPUep4GjGdQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Sat, Aug 1, 2020 at 2:16 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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.

While I like having HP-UX buildfarm coverage, the status page says
that gaur is running 10.20, which according to noted reliable source
Wikipedia, was released in 1996 and went out of support in 2003. So I
wonder whether testing that version is really a sensible thing to do
at this point.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2020-08-03 16:11:58 Re: pgsql: Fix some issues with step generation in partition pruning.
Previous Message Tom Lane 2020-08-03 13:46:25 pgsql: Fix behavior of ecpg's "EXEC SQL elif name".