Horton

Re: Reducing memory consumed by RestrictInfo list translations in partitionwise join planning

Alvaro Herrera <alvherre@alvh.no-ip.org>

View thread
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: David Rowley <dgrowleyml@gmail.com>
Cc: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>, Amit Langote <amitlangote09@gmail.com>, Dmitry Dolgov <9erthalion6@gmail.com>, tomas@vondra.me, vignesh C <vignesh21@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>, Richard Guo <guofenglinux@gmail.com>
Date: 2025-03-28T17:16:29Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Add assertion to verify derived clause has constant RHS

  2. Make derived clause lookup in EquivalenceClass more efficient

  3. Doc: improve documentation for jsonpath behavior.

  4. Work around implementation restriction in adjust_appendrel_attrs.

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/