Re: First draft of PG 19 release notes

On Wed, Apr 22, 2026 at 11:10:06AM +0800, jian he wrote:
> On Wed, Apr 15, 2026 at 9:19 AM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> >
> > I have completed the first draft of the PG 19 release notes:
> >
> > https://www.postgresql.org/docs/devel/release-19.html
> >
>
> Change FDW function prototypes to use uint* instead of bit* typedefs
> (Nathan Bossart) §
> This commit doesn't seem related to FDW?

Wow, I have no idea why I put FDW in there. Next text is:

Change function prototypes to use uint* instead of bit* typedefs (Nathan
Bossart)

> Allow btree_gin to match partial qualifications (Tom Lane) § §
> I don't understand "partial qualifications", the commit seems more
> about "cross type operators".

Yeah, another mistake. I got the description from this doc change in
the patch:

+ Compare a partial-match query key to an index key.
+ <literal>partial_key</literal> is a query key that was returned
+ by <function>extractQuery</function> with an indication that it
+ requires partial match, and <literal>key</literal> is an index entry.
+ Returns an integer

but that is only a clarification of an existing sentence, and I mistook
that for a new feature. If a patch has a doc change, I tend to focus on
that, but made a mistake here. New text is:

Change btree_gin to support all btree-supported cross-type comparisons
(Tom Lane)

> https://git.postgresql.org/cgit/postgresql.git/commit/?id=999f172d
> Can this also be added to the release notes?

Uh, I saw that one, and I don't normally mention changes where rare
actions used to generate errors, and don't anymore, and I saw this one
as being in that category.

> Do you think this
> (https://git.postgresql.org/cgit/postgresql.git/commit/?id=00c025a001170979e99706ce746f75fcc615761d)
> worth add to the release notes?
>
> Before commit:
> https://www.postgresql.org/docs/current/functions-matching.html#FUNCTIONS-POSIX-REGEXP
> After commit:
> https://www.postgresql.org/docs/devel/functions-matching.html#FUNCTIONS-POSIX-LIST

I saw this as a documentation restructuring, and I usually only mention
document changes that create significant new content.

Attached patch applied.

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

Do not let urgent matters crowd out time for investment in the future.