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

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PSA: Planning to grease protocol connections during 19beta
Date: 2026-06-03 18:38:00
Message-ID: CAOYmi+mcu8dhqPe4+iSFsOdUAkYgsff3nCUzTF8mDKzPTX4B6g@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jun 3, 2026 at 1:04 AM Jelte Fennema-Nio <postgres(at)jeltef(dot)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(at)lists(dot)postgresql(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Champion 2026-06-03 18:53:26 Re: Heads Up: cirrus-ci is shutting down June 1st
Previous Message Peter Eisentraut 2026-06-03 18:34:41 Re: Heads Up: cirrus-ci is shutting down June 1st