Re: Add missing period to HINT messages

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: Robert Treat <rob@xzilla.net>, Amit Kapila <amit.kapila16@gmail.com>, Peter Smith <smithpb2250@gmail.com>, Chao Li <li.evan.chao@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-04-14T01:07:25Z
Lists: pgsql-hackers
"David G. Johnston" <david.g.johnston@gmail.com> writes:
> I was under the impression that on both user-facing behavior changes
> grounds, and translation grounds, back-patching changes to existing
> messages is not allowed absent a true factual bug.

"Not allowed" is a bit strong, but yeah we don't usually mess with
translatable strings in back branches without a pretty good reason.
The translators have enough work as it is.

			regards, tom lane



Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Add missing period to HINT messages.

  2. Add test case for same-type reordered FK columns