From: Noah Misch <noah@leadboat.com>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Fix attach of a previously-detached injection point.
Date: Thu, 22 Aug 2024 07:09:17 +0000
Message-ID: <E1sh1wb-000tKo-Ht@gemulon.postgresql.org> (raw)
Fix attach of a previously-detached injection point.
It's normal for the name in a free slot to match the new name. The
max_inuse mechanism kept simple cases from reaching the problem. The
problem could appear when index 0 was the previously-detached entry and
index 1 is in use. Back-patch to v17, where this code first appeared.
Branch
------
REL_17_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/6b1f78d90b5f2475d968e16febee8f9d43730d63
Modified Files
--------------
src/backend/utils/misc/injection_point.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: noah@leadboat.com, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Fix attach of a previously-detached injection point.
In-Reply-To: <E1sh1wb-000tKo-Ht@gemulon.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox