Re: Add missing period to HINT messages

David G. Johnston <david.g.johnston@gmail.com>

From: "David G. Johnston" <david.g.johnston@gmail.com>
To: Robert Treat <rob@xzilla.net>
Cc: 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:00:16Z
Lists: pgsql-hackers
On Monday, April 13, 2026, Robert Treat <rob@xzilla.net> wrote:

>
>
> I don't have a strong opinion on it, but I think generally that clean
> up patches (where we aren't fixing some kind of document mistake or
> misleading information) generally just go into HEAD for the next
> release, though if it easily applies cleanly to back branches and you
> want to do it, it's probably ok to apply it backwards, but I wouldn't
> spend any time on it if it didn't.
>

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.

David J.

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