pgsql: Fix plancache refcount leak after error in ExecuteQuery. - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Fix plancache refcount leak after error in ExecuteQuery.
Date
Msg-id E1ltezS-0003x8-SG@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Fix plancache refcount leak after error in ExecuteQuery.

When stuffing a plan from the plancache into a Portal, one is
not supposed to risk throwing an error between GetCachedPlan and
PortalDefineQuery; if that happens, the plan refcount incremented
by GetCachedPlan will be leaked.  I managed to break this rule
while refactoring code in 9dbf2b7d7.  There is no visible
consequence other than some memory leakage, and since nobody is
very likely to trigger the relevant error conditions many times
in a row, it's not surprising we haven't noticed.  Nonetheless,
it's a bug, so rearrange the order of operations to remove the
hazard.

Noted on the way to looking for a better fix for bug #17053.
This mistake is pretty old, so back-patch to all supported
branches.

Branch
------
REL_12_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/17d962ccae33db4526d08f909eea536a2a2383cf

Modified Files
--------------
src/backend/commands/prepare.c | 18 +++++++++++-------
1 file changed, 11 insertions(+), 7 deletions(-)


pgsql-committers by date:

Previous
From: Tomas Vondra
Date:
Subject: pgsql: Fix copying data into slots with FDW batching
Next
From: Michael Paquier
Date:
Subject: pgsql: Remove dry-run mode from isolationtester