Postgres Pro
Downloads
Home   >   mailing lists

Re: Result Cache node shows per-worker info even for workers not launched - Mailing list pgsql-hackers

From Amit Khandekar
Subject Re: Result Cache node shows per-worker info even for workers not launched
Date
Msg-id CAJ3gD9dAhJ945HgMXG2mZVX2euJmc5yEq1ngzj9jQPkxqUSF+g@mail.gmail.com
Whole thread Raw
In response to Re: Result Cache node shows per-worker info even for workers not launched  (David Rowley <dgrowleyml@gmail.com>)
Responses Re: Result Cache node shows per-worker info even for workers not launched  (David Rowley <dgrowleyml@gmail.com>)
List pgsql-hackers
Tree view 
On Wed, 28 Apr 2021 at 13:54, David Rowley <dgrowleyml@gmail.com> wrote:

> So, given that I removed the parallel test in partition_prune.sql, and
> don't have any EXPLAIN ANALYZE output for parallel tests in
> resultcache.sql, it should be safe enough to put that cache_misses ==
> 0 test back into explain.c
>
> I've attached a patch to do this. The explain.c part is pretty similar
> to your patch, I just took my original code and comment.

Sounds good. And thanks for the cleanup patch, and the brief history.
Patch looks ok to me.

pgsql-hackers by date:

Previous
From: Amit Khandekar
Date:
Subject: Re: Result Cache node shows per-worker info even for workers not launched
Next
From: Masahiko Sawada
Date:
Subject: Re: Replication slot stats misgivings