Request a Demo
Home   >   mailing lists

Re: Memory leak in pg_stat_statements when qtext file contains invalid encoding - Mailing list pgsql-bugs

From Lukas Fittl
Subject Re: Memory leak in pg_stat_statements when qtext file contains invalid encoding
Date
Msg-id CAP53PkwciXaP2TQLjkjLGHD1+HEtBfCcpfd25xCnGbgQErpocA@mail.gmail.com
Whole thread Raw
In response to Re: Memory leak in pg_stat_statements when qtext file contains invalid encoding  (Heikki Linnakangas <hlinnaka@iki.fi>)
List pgsql-bugs
Tree view 
On Fri, Mar 27, 2026 at 4:13 AM Heikki Linnakangas <hlinnaka@iki.fi> wrote:
>
> On 27/03/2026 11:05, Daniel Gustafsson wrote:
> >> On 27 Mar 2026, at 09:59, Heikki Linnakangas <hlinnaka@iki.fi> wrote:
> >
> >> Hmm, perhaps. But there's a simpler, less invasive fix. When that code was written, we didn't have MCXT_ALLOC_HUGE
norMCXT_ALLOC_NO_OOM. Now that we do, we can just use palloc_extended(MCXT_ALLOC_HUGE | MCXT_ALLOC_NO_OOM) instead of
rawmalloc(). Per attached. 
> >
> > LGTM.
>
> Committed, thanks!

Thanks for the quick fix!

TIL about MCXT_ALLOC_NO_OOM, that's useful to know about.

Thanks,
Lukas

--
Lukas Fittl

pgsql-bugs by date:

Previous
From: Dmytro Astapov
Date:
Subject: array_agg(anyarray) silently produces corrupt results with parallel workers when inputs mix NULL and non-NULL array elements
Next
From: Tom Lane
Date:
Subject: Re: BUG #19438: segfault with temp_file_limit inside cursor