Re: PSA: Planning to grease protocol connections during 19beta
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jacob Champion <jacob.champion@enterprisedb.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>,
Jelte Fennema-Nio <postgres@jeltef.nl>
Date: 2026-02-23T20:20:13Z
Lists: pgsql-hackers
Jacob Champion <jacob.champion@enterprisedb.com> writes: > 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? We have the ability to lock down a wiki page, but I believe that means nobody can edit it until a wiki admin unlocks it. That might be the way to go here though. I concur with your reasoning that the main docs are a less-good place. 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 →
-
libpq: Send users to the wiki during grease failures
- 2368c14e9e20 19 (unreleased) landed