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

From Michael Paquier
Subject Re: Fix memory leak in gist_page_items() of pageinspect
Date
Msg-id aUSH4oyxfLSpRRZ4@paquier.xyz
Whole thread Raw
In response to Re: Fix memory leak in gist_page_items() of pageinspect  (Bertrand Drouvot <bertranddrouvot.pg@gmail.com>)
Responses Re: Fix memory leak in gist_page_items() of pageinspect
List pgsql-hackers
On Wed, Dec 17, 2025 at 11:57:13AM +0000, Bertrand Drouvot wrote:
> Please note that for hash_bitmap_info() and pgstathashindex() the open calls are
> changed instead. For those we keep the IS_INDEX() checks to reject partitioned
> indexes (which index_open() accepts via validate_relation_kind()). So, that also
> changes the error messages in some tests. If we do prefer the previous error
> messages we could change the close calls instead (I prefer the way it's done
> in the attached though).

I have noticed that the two surrounding relation_close() calls for the
parent tables did not get the notice of the change for brin.c of what
you are doing for the indexes, while we use table_open().  I have
fixed these.

It would be nicer if IS_INDEX() could be removed in the other code
paths you are suggesting to change, but the partitioned index argument
also means that we would have two code paths in charge of a relkind
check instead of one.  Just using relation_*() may be cleaner.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Fwd: [PATCH] Add zstd compression for TOAST using extended header format
Next
From: Masahiko Sawada
Date:
Subject: Re: Proposal: Conflict log history table for Logical Replication