Re: PSA: Planning to grease protocol connections during 19beta
Jacob Champion <jacob.champion@enterprisedb.com>
From: Jacob Champion <jacob.champion@enterprisedb.com>
To: Jelte Fennema-Nio <postgres@jeltef.nl>
Cc: Tom Lane <tgl@sss.pgh.pa.us>,
PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2026-06-03T18:38:00Z
Lists: pgsql-hackers
On Wed, Jun 3, 2026 at 1:04 AM Jelte Fennema-Nio <postgres@jeltef.nl> wrote: > 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 Thanks! Something like that seems reasonable to me, yeah. Any objections here to making -hackers the landing point? I wouldn't want to do that for a released feature, but for a beta-only thing, I feel like the audience will be small enough to avoid accidentally DoSing ourselves. --Jacob
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