| From: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
|---|---|
| To: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
| 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 08:03:55 |
| Message-ID: | CAGECzQTEjzD=K3YzoJnNV0z33ADsqcrYC1xdt_cd8h+PS+0RKg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Apr 13, 2026, 20:58 Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)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(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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro Horiguchi | 2026-06-03 08:10:39 | Re: Improve pg_stat_statements scalability |
| Previous Message | Japin Li | 2026-06-03 07:58:01 | Use TEXT_DUMP_HEADER macro instead of hard-coded string in pg_backup_archiver.c |