From: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | pgsql: dbase_redo: Fix Valgrind-reported memory leak |
Date: | 2025-10-11 14:48:27 |
Message-ID: | [email protected] |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
dbase_redo: Fix Valgrind-reported memory leak
Introduced by my (Álvaro's) commit 9e4f914b5eba, which was itself
backpatched to pg10, though only pg15 and up contain the problem
because of commit 9c08aea6a309.
This isn't a particularly significant leak, but given the fix is
trivial, we might as well backpatch to all branches where it applies, so
do that.
Author: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Reported-by: Andres Freund <andres(at)anarazel(dot)de>
Discussion: https://postgr.es/m/x4odfdlrwvsjawscnqsqjpofvauxslw7b4oyvxgt5owoyf4ysn@heafjusodrz7
Branch
------
REL_16_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/c72b5c536032d636cf35d964c216c3e44e2b1efe
Modified Files
--------------
src/backend/commands/dbcommands.c | 1 +
1 file changed, 1 insertion(+)
From | Date | Subject | |
---|---|---|---|
Next Message | Álvaro Herrera | 2025-10-11 18:31:06 | pgsql: Stop creating constraints during DETACH CONCURRENTLY |
Previous Message | Peter Geoghegan | 2025-10-10 18:52:38 | pgsql: Remove overzealous _bt_killitems assertion. |