Re: Add missing period to HINT messages

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

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Chao Li <li.evan.chao@gmail.com>
Cc: Robert Treat <rob@xzilla.net>, Amit Kapila <amit.kapila16@gmail.com>, Peter Smith <smithpb2250@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-04-14T01:18:29Z
Lists: pgsql-hackers
Chao Li <li.evan.chao@gmail.com> writes:
> I don’t see a branch for 19 is cut out, so is HEAD still 19 today?

Yes.  We typically don't make the branch until after beta1.
It definitely has to happen before the first CF for the new cycle
opens, but up till that point we tend to think it'd just double
the committing work for bug fixes, as well as encourage people
to work on new development at a time they should be working on
stabilizing/testing the release.

In recent years it's tended to happen late June (grep the commit
log for "Stamp HEAD as ...").

			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