Re: pgsql: Improve accounting for memory used by shared hash tables

From: Tomas Vondra <tomas(at)vondra(dot)me>
To: David Rowley <dgrowleyml(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)postgresql(dot)org>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Improve accounting for memory used by shared hash tables
Date: 2025-04-04 00:41:40
Message-ID: 46c20602-41e3-47b7-aa1d-7d1d2478e4f6@vondra.me
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On 4/4/25 01:43, Tomas Vondra wrote:
> On 4/4/25 00:57, David Rowley wrote:
>> On Thu, 3 Apr 2025 at 04:16, Tomas Vondra <tomas(dot)vondra(at)postgresql(dot)org> wrote:
>>> Improve accounting for memory used by shared hash tables
>>
>> I've not looked into why, but this is causing an issue in the
>> join_rel_hash during add_join_rel(). See the attached script.
>>
>> ERROR: pfree called with invalid pointer 0x60a15edc44e0 (header
>> 0x0000002000000008)
>>
>
> Thanks for the report and reproducer. I'll take a look tomorrow.
>

I took a quick look, and I think the reason is fairly simple - the
commit allocates the header and the directory as a single chunk. And for
shared hash tables that's fine, because those have non-expandable
directory. But the patch does the same thing for non-shared hash tables
(not intentionally), which means that if we end up expanding the hash,
it fails in dir_realloc(). Because hashp->dir is not a separately
allocated chunk.

This is clearly a bug in the patch, I should have caught this during a
review. But I'm also quite surprised none of the regression tests seems
to expand the hash table ...

I'll think about a way to fix this tomorrow.

--
Tomas Vondra

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Amit Langote 2025-04-04 02:34:48 pgsql: Add assertion to verify derived clause has constant RHS
Previous Message Tomas Vondra 2025-04-03 23:43:24 Re: pgsql: Improve accounting for memory used by shared hash tables