Re: [PATCH] Fix Potential Memory Leak in pg_amcheck Code - Mailing list pgsql-hackers

From Kirill Reshke
Subject Re: [PATCH] Fix Potential Memory Leak in pg_amcheck Code
Date
Msg-id CALdSSPjvPr7QNNwPB4i=sF6eaZO=j53m+aj+WqHPi0rUbJd9Ew@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Fix Potential Memory Leak in pg_amcheck Code  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: [PATCH] Fix Potential Memory Leak in pg_amcheck Code
List pgsql-hackers
Hi!

On Fri, 7 Feb 2025 at 13:28, Daniel Gustafsson <daniel@yesql.se> wrote:
>
> That being said, there is
> value in doing the right thing and setting good examples in our own code as
> many do read it and reference it.

> We call PQclear on such a
> case elsewhere in the file so it's not entirely consistent, but it's not all
> that important as the memory will be reclaimed at exit.

So, are we +1 or -1 on moving this forward?

-- 
Best regards,
Kirill Reshke



pgsql-hackers by date:

Previous
From: Peter Smith
Date:
Subject: Re: Proposal: Filter irrelevant change before reassemble transactions during logical decoding
Next
From: Amit Langote
Date:
Subject: Re: generic plans and "initial" pruning