Request a Demo
Home   >   mailing lists

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

From Daniel Gustafsson
Subject Re: Memory leak in pg_stat_statements when qtext file contains invalid encoding
Date
Msg-id 56D5EAF1-1636-45EC-97FB-3A08260417D2@yesql.se
Whole thread Raw
In response to Re: Memory leak in pg_stat_statements when qtext file contains invalid encoding  (Heikki Linnakangas <hlinnaka@iki.fi>)
Responses Re: Memory leak in pg_stat_statements when qtext file contains invalid encoding
List pgsql-bugs
Tree view 
> 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.

--
Daniel Gustafsson

pgsql-bugs by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Memory leak in pg_stat_statements when qtext file contains invalid encoding
Next
From: Sérgio Duarte
Date:
Subject: Re: POSTGIS | SQL Error [42501]: ERROR: permission denied to create "pg_catalog.geometry_dump"