Re: Result Cache node shows per-worker info even for workers not launched

From: Amit Khandekar <amitdkhan(dot)pg(at)gmail(dot)com>
To: David Rowley <dgrowleyml(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Result Cache node shows per-worker info even for workers not launched
Date: 2021-04-28 11:05:16
Message-ID: CAJ3gD9dAhJ945HgMXG2mZVX2euJmc5yEq1ngzj9jQPkxqUSF+g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 28 Apr 2021 at 13:54, David Rowley <dgrowleyml(at)gmail(dot)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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2021-04-28 11:21:21 Re: Replication slot stats misgivings
Previous Message Amit Khandekar 2021-04-28 10:59:09 Re: Result Cache node shows per-worker info even for workers not launched