Re: Hybrid Hash/Nested Loop joins and caching results from subplans

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Andy Fan <zhihui(dot)fan1213(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Hybrid Hash/Nested Loop joins and caching results from subplans
Date: 2020-08-03 22:05:25
Message-ID: CAApHDvqFLXXge153WmPsjke5VGOSt7Ez0yD0c7eBXLfmWxs3Kw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 8 Jul 2020 at 15:37, David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
> The attached v5 patch set fixes that.

I've attached an updated set of patches for this per recent conflict.

I'd like to push the 0002 patch quite soon as I think it's an
improvement to simplehash.h regardless of if we get Result Cache. It
reuses the SH_LOOKUP function for deletes. Also, if we ever get around
to giving up performing a lookup if we get too far away from the
optimal bucket, then that would only need to appear in one location
rather than in two.

Andres, or anyone, any objections to me pushing 0002?

David

Attachment Content-Type Size
v6-0002-Allow-users-of-simplehash.h-to-perform-direct-del.patch application/octet-stream 5.2 KB
v6-0001-Allow-estimate_num_groups-to-pass-back-further-de.patch application/octet-stream 8.8 KB
v6-0003-Add-Result-Cache-executor-node.patch application/octet-stream 156.0 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2020-08-03 22:44:03 Re: psql - improve test coverage from 41% to 88%
Previous Message Bruce Momjian 2020-08-03 21:02:14 Re: PG 13 release notes, first draft