From: Peter Eisentraut <peter@eisentraut.org>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Correct misleading error messages
Date: Thu, 26 Jun 2025 20:04:21 +0000
Message-ID: <E1uUspY-003TeF-2w@gemulon.postgresql.org> (raw)
Correct misleading error messages
Commit 7d6d2c4bbd7 dropped opcintype from the index AM strategy
translation API. But some error messages about failed lookups still
mentioned it, even though it was not used for the lookup. Fix by
removing ipcintype from the error messages as well.
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/95e12d4d9b228855af8a2a34ca28c33924d4edd1
Modified Files
--------------
src/backend/commands/indexcmds.c | 4 ++--
src/backend/commands/tablecmds.c | 4 ++--
2 files changed, 4 insertions(+), 4 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: peter@eisentraut.org, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Correct misleading error messages
In-Reply-To: <E1uUspY-003TeF-2w@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