From: Robert Haas <rhaas@postgresql.org>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Fix non-specific error message.
Date: Thu, 11 Aug 2022 18:12:18 +0000
Message-ID: <E1oMCfJ-000JEP-BF@gemulon.postgresql.org> (raw)
Fix non-specific error message.
"something has gone wrong" is not helpful. Make this elog()
consistent with the other one in the same function.
Discussion: http://postgr.es/m/CA+Tgmoa_AZ2jUWSA_noiqOqnxBaWDR+t3bHjSygZi6+wqDBCXQ@mail.gmail.com
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/34dffa0224bd34e0fa27b464f1821c9c43f07703
Modified Files
--------------
src/backend/postmaster/auxprocess.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-committers@postgresql.org
Cc: rhaas@postgresql.org
Subject: Re: pgsql: Fix non-specific error message.
In-Reply-To: <E1oMCfJ-000JEP-BF@gemulon.postgresql.org>
References: <E1oMCfJ-000JEP-BF@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