Re: pgsql: Add Result Cache executor node

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Rowley <dgrowleyml(at)gmail(dot)com>
Cc: David Rowley <drowley(at)postgresql(dot)org>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Add Result Cache executor node
Date: 2021-04-01 00:52:00
Message-ID: 3346528.1617238320@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

David Rowley <dgrowleyml(at)gmail(dot)com> writes:
> On Thu, 1 Apr 2021 at 12:32, David Rowley <drowley(at)postgresql(dot)org> wrote:
>> Add Result Cache executor node

> I'm not really sure why yet why many buildfarm members don't like this.

Something that struck me is that the animals that stayed green were
almost exclusively Debian and macOS, while the unhappy ones were
uniformly not. That pattern makes no sense --- why would Debian
act differently from other Linuxen? --- but it sure seems real.

[ looks a bit more... ] Actually, most of those Debian machines
are Andres' test menagerie. So maybe there's some commonality
of configuration of his animals that is connected to this.

Anyway, it looks like I can probably reproduce it on florican's
host, if you still need help understanding it tomorrow. But
I remain really dubious that this can work at all. Question:
have you tried that test under CLOBBER_CACHE_ALWAYS?

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2021-04-01 00:54:37 pgsql: Move some client-specific routines from SSLServer to PostgresNod
Previous Message David Rowley 2021-04-01 00:33:43 pgsql: Revert b6002a796