Re: Memory leak in pg_stat_statements when qtext file contains invalid encoding

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: Lukas Fittl <lukas(at)fittl(dot)com>, Gaurav Singh <gaurav(dot)singh(at)yugabyte(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Memory leak in pg_stat_statements when qtext file contains invalid encoding
Date: 2026-03-27 09:05:18
Message-ID: 56D5EAF1-1636-45EC-97FB-3A08260417D2@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> On 27 Mar 2026, at 09:59, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:

> Hmm, perhaps. But there's a simpler, less invasive fix. When that code was written, we didn't have MCXT_ALLOC_HUGE nor MCXT_ALLOC_NO_OOM. Now that we do, we can just use palloc_extended(MCXT_ALLOC_HUGE | MCXT_ALLOC_NO_OOM) instead of raw malloc(). Per attached.

LGTM.

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Sérgio Duarte 2026-03-27 11:05:22 Re: POSTGIS | SQL Error [42501]: ERROR: permission denied to create "pg_catalog.geometry_dump"
Previous Message Heikki Linnakangas 2026-03-27 08:59:32 Re: Memory leak in pg_stat_statements when qtext file contains invalid encoding