| From: | Quan Zongliang <quanzongliang(at)yeah(dot)net> |
|---|---|
| To: | Tatsuya Kawata <kawatatatsuya0913(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Remove stale comment and dead store in BuildTupleHashTable |
| Date: | 2026-08-12 09:31:15 |
| Message-ID: | 63ec33c0-0631-4a6b-9f14-522b823f7c8d@yeah.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 8/11/26 10:01 AM, Quan Zongliang wrote:
>
>
> On 8/9/26 7:22 PM, Tatsuya Kawata wrote:
>> Hi,
>>
>> While reading the aggregation-related executor code, I noticed a comment
>> that no longer matches what the code does.
>>
>> In BuildTupleHashTable() (src/backend/executor/execGrouping.c) we have:
>>
>> hashtable->tableslot = NULL; /* will be made on first lookup */
>>
> This initialization was initially introduced in the patch f97aebd1.
> The hashtable->tableslot is initialized in the LookupTupleHashEntry
> function.
>
>> The slot is no longer made on first lookup. Commit bf6c614a2f2 removed
>> the lazy creation from LookupTupleHashEntry() and made
>> BuildTupleHashTable() create the slot unconditionally, further down in
>> the same function. Only the comment and its assignment were left behind.
>>
>
> It also involves patch 773aec7a and its revert patch 2a41507d
>
> Initialization is no longer necessary.
>
This is a very clear and straightforward code refactoring. There won't
be any objections. Change to "Ready for Committer".
--
Quan Zongliang
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2026-08-12 09:34:33 | Re: WAL compression setting after PostgreSQL LZ4 default change |
| Previous Message | Ayush Tiwari | 2026-08-12 09:27:33 | Re: Backup manifests accept out-of-range LSNs |