Re: PSA: Planning to grease protocol connections during 19beta
Jacob Champion <jacob.champion@enterprisedb.com>
From: Jacob Champion <jacob.champion@enterprisedb.com>
To: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Cc: Jelte Fennema-Nio <postgres@jeltef.nl>
Date: 2026-02-23T20:00:49Z
Lists: pgsql-hackers
On Tue, Dec 9, 2025 at 5:16 PM Jacob Champion <jacob.champion@enterprisedb.com> wrote: > I want to make sure this doesn't take anyone by surprise: I'm planning > to get Jelte's "grease" patch into shape for a commit some time in > January. As of January 54th, this is committed. I wanted to get people's thoughts on communication. As it stands now, beta users will be directed towards our own documentation [1] when they hit a grease failure. But personally, I'd like the landing page to be on the wiki, for several reasons: - It can be written in a more casual voice, and go into detail that would be out of place in a docs note - It's easier to change quickly in response to end user feedback, if we receive any - It can remain in place after the beta period ends But having libpq link to a wiki page makes that page a vandalism target. Can a wiki page be protected in a way that still lets committers edit it? Is there a third option that works better than the docs or the wiki? --Jacob [1] https://www.postgresql.org/docs/devel/libpq-connect.html#LIBPQ-CONNECT-MAX-PROTOCOL-VERSION
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
libpq: Send users to the wiki during grease failures
- 2368c14e9e20 19 (unreleased) landed