Re: PSA: Planning to grease protocol connections during 19beta

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Cc: Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>
Subject: Re: PSA: Planning to grease protocol connections during 19beta
Date: 2026-08-25 16:23:03
Message-ID: CAOYmi+kWMBfz5LzQd0W8V5pScLE-1GTxqyMyQOKY9wS41-RYtQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Dec 9, 2025 at 5:16 PM Jacob Champion
<jacob(dot)champion(at)enterprisedb(dot)com> wrote:
> The plan is to grease the minor version number and at least one
> protocol extension during the 19 beta, then revert partway through (as
> tracked by a mid-beta Open Item).

And now it's time to revert. Proposed patch attached.

Though we didn't get any [grease] emails to the list, I think this was
a success. There are recent issues and PRs on GitHub that reference
this, and we flushed out an issue with Debian's upgrade wrappers that
matches the bug that pg_upgrade itself had, and there's even anecdotal
evidence that a correct negotiation implementation can survive contact
with Copilot's incorrect review advice. Woohoo!

Jelte, thanks again for the idea. I think we should try to develop a
production implementation of this for PG20.

--Jacob

Attachment Content-Type Size
0001-libpq-Stop-greasing-protocol-connections.patch application/octet-stream 12.7 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2026-08-25 16:33:46 Re: Error handling in after-startup shmem requests
Previous Message Alberto Piai 2026-08-25 16:13:05 Re: Adding a stored generated column without long-lived locks