Re: Reduce memory overheads for storing a Memoize tuple

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: David Rowley <dgrowleyml(at)gmail(dot)com>, Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Reduce memory overheads for storing a Memoize tuple
Date: 2026-08-21 15:30:03
Message-ID: 9E4500E4-63A4-426D-A898-31E6985EC9EE@yandex-team.ru
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 21 Aug 2026, at 10:20, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> All CI runs are failing for the 32-bit
> meson task.

Hi David, Michael,

I hit the same failure while running bunch of CI tasks today for an unrelated
patch. So decided maybe a little patch could be helpful. I used this to calm
CI of my stuff.

The thing is 1000 small cache entries now fit in the minimum work_mem, so the
test reports no evictions.
PFA a fix that uses COUNT(t1), making Memoize cache the whole inner tuple.

Best regards, Andrey Borodin.

Attachment Content-Type Size
0001-Make-Memoize-eviction-test-work-on-32-bit-builds.patch application/octet-stream 2.9 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavlo Golub 2026-08-21 15:31:24 Re: [PATCH] Add pg_current_vxact_id() function to expose virtual transaction IDs
Previous Message Tom Lane 2026-08-21 15:20:28 Re: Allow a prosupport function to be attached to an aggregate