| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
| Cc: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, Amit Langote <amitlangote09(at)gmail(dot)com>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, tomas(at)vondra(dot)me, vignesh C <vignesh21(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Richard Guo <guofenglinux(at)gmail(dot)com> |
| Subject: | Re: Reducing memory consumed by RestrictInfo list translations in partitionwise join planning |
| Date: | 2025-03-28 17:16:29 |
| Message-ID: | 202503281716.67ufbgpv76pj@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2025-Mar-28, David Rowley wrote:
> I experimented by applying your v4 along with 0001-0003 of Yuya's v35
> patchset from [2]. See the attached bz2 for my results run on an AMD
> Zen2 machine. The CREATE TABLE statement is in the attached script.
Eyeballing these results, unless I am misreading them, the patch brings
zero benefit.
With PWJ off, there's no plan time improvement and no memory consumption
improvement either; only with Watari-san's patch there's an improvement
in plan time (and with Watari's patch, I see negligible difference
between the case with 64 buckets and the other case, which I assume has
256 buckets). But the "master" vs. "v4_patch" cases seem to be
essentially identical.
With PWJ on, the situation is the same. master_pwj looks pretty much
the same as v4_pwj.
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2025-03-28 17:47:16 | Re: pg_stat_database.checksum_failures vs shared relations |
| Previous Message | Ashutosh Bapat | 2025-03-28 16:46:15 | Re: Reducing memory consumed by RestrictInfo list translations in partitionwise join planning |