Re: tuplesort_putdatum() does not account for tuple memory

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Mario Karuza <mkaruza(dot)pg(at)icloud(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: tuplesort_putdatum() does not account for tuple memory
Date: 2026-10-05 12:23:43
Message-ID: CAApHDvq1eCf4=j+jp4ZGOTsqBUSk=JJHi3zWMmULOgw3gQRu4A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 5 Oct 2026 at 19:59, Mario Karuza <mkaruza(dot)pg(at)icloud(dot)com> wrote:
> Sure, there was no production issue, it was driven by exploration if AIO
> subsystem and if it can be used around spilling. Noticed `still in
> progress` from EXPLAIN ANALYZE output, used AI agent to understand
> execution path and there was fixed argument that was passed to function.
> Commit 6ed83d5fa55 covered other paths but not this one.

Thanks. I've pushed your patch and backpatched to v17.

David

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Gustafsson 2026-10-05 12:26:17 Re: Serverside SNI support in libpq
Previous Message Joao Detomini 2026-10-05 12:18:56 Re: doc: Document Linux cgroup memory limits