Re: PSA: Planning to grease protocol connections during 19beta
Jelte Fennema <postgres@jeltef.nl>
From: Jelte Fennema-Nio <postgres@jeltef.nl>
To: Jacob Champion <jacob.champion@enterprisedb.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>,
PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2026-06-03T08:03:55Z
Lists: pgsql-hackers
On Mon, Apr 13, 2026, 20:58 Jacob Champion <jacob.champion@enterprisedb.com> wrote: > Something I'm struggling with is whether (and how) to have people let > us know when they've hit this, so that we know that the campaign is > working. I have some language to that effect in the "What do I need to > do?" section, but I don't really know what list I should point to, if > any, nor what they should say so that they don't confuse the list > regulars. I'm considering removing that part of the call to action. > I think it'd be good if they notify us too. So we can get a sense of whether it's "safe enough" to bump the protocol version at some point and/or we can bug important offenders that we have some sway over. How about adding something like this to the wiki page: Please also report the issue to the pgsql-hackers mailinglist using the [grease] tag at the start of the subject and include a link to the upstream issue (if it's on a public issue tracker). As an example: To: pgsql-hackers@lists.postgresql.org Subject: [grease] ExampleProxy fails grease check Body: I'm using ExampleProxy and it's failing the grease check. I've reported the issue upstream at https://example.com/issues/1234
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