Re: Fix memory leak in gist_page_items() of pageinspect - Mailing list pgsql-hackers

From Chao Li
Subject Re: Fix memory leak in gist_page_items() of pageinspect
Date
Msg-id 5484DB5D-813C-4743-8BD1-7DF677FA5D98@gmail.com
Whole thread Raw
In response to Re: Fix memory leak in gist_page_items() of pageinspect  (Bertrand Drouvot <bertranddrouvot.pg@gmail.com>)
List pgsql-hackers

> On Dec 19, 2025, at 18:26, Bertrand Drouvot <bertranddrouvot.pg@gmail.com> wrote:
>
> Hi,
>
> On Fri, Dec 19, 2025 at 05:36:51PM +0800, Japin Li wrote:
>> On Fri, 19 Dec 2025 at 08:23, Bertrand Drouvot <bertranddrouvot.pg@gmail.com> wrote:
>>> Yeah that would not hurt. What about before the relation_open() calls?
>>>
>>> "
>>> Use relation_open() and not index_open() to avoid the validate_relation_kind()
>>> check as we handle relation validation separately below.
>>> "
>>>
>>
>> LGTM.
>
> Thanks! Done that way in the attached.
>
> Regards,
>
> --
> Bertrand Drouvot
> PostgreSQL Contributors Team
> RDS Open Source Databases
> Amazon Web Services: https://aws.amazon.com
> <v3-0001-Use-relation_close-more-consistently.patch>

LGTM. As the immediately following statement is if (!IS_INDEX(rel)), adding a comment to relation_open() feels very
necessary.

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/







pgsql-hackers by date:

Previous
From: Kevin K Biju
Date:
Subject: Allowing ALTER COLUMN TYPE for columns in publication column lists
Next
From: Chao Li
Date:
Subject: Re: A few patches to clarify snapshot management, part 2