Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wUgaD-001McL-16 for pgsql-hackers@arkaria.postgresql.org; Wed, 03 Jun 2026 08:04:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wUgaB-000Oq9-2R for pgsql-hackers@arkaria.postgresql.org; Wed, 03 Jun 2026 08:04:11 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wUgaB-000Oq1-0r for pgsql-hackers@lists.postgresql.org; Wed, 03 Jun 2026 08:04:11 +0000 Received: from mail-lf1-x136.google.com ([2a00:1450:4864:20::136]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.98.2) (envelope-from ) id 1wUga9-00000000sYH-0U86 for pgsql-hackers@postgresql.org; Wed, 03 Jun 2026 08:04:10 +0000 Received: by mail-lf1-x136.google.com with SMTP id 2adb3069b0e04-5aa6792e7b8so3373206e87.1 for ; Wed, 03 Jun 2026 01:04:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1780473847; cv=none; d=google.com; s=arc-20240605; b=BrWGSYLLQNRGFMSceKWk33B97R5j67wbZFpl9lNynJ0/oXfD9A3qfHknWfjXEDje+8 xDH9llboun4+3lfLtv5GTi6fg1MTS16eaTVQ0Nfa6pQ1fcGt2g3ffZg7yGh2d45kcLg8 usBO2i1oTLs3LG/etAl53wDlGy3ZB4yYMQ5agbCcQbfV08eJBG3Wu/7uG5BxC2ACgCkX yTEPhbalO9AbA6DwyazNNRJC9kGhWpqBaZbvjKRnMc0dIGJUvbgZdQ8rAKZLZ6nDR05/ jyyjlUOP/OUFu/255MmQUsTTE65nbCbsL/Yue12T43/blRrzaY0l8gOm0yTB79G7bhgG P26w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:dkim-signature; bh=72xThpgFP8Ph64tij2zcAcFdlltZXe4bLTNOjXfOcbo=; fh=k6lMsEQYqX4RCejut8dTBpIBOZYVPesdXUu4CCbFJFU=; b=Bp2x/Ry09GmPIHJJvyRcTgn+Li++HxIKf8L/k3RSD98xMkL0ToDTNqFPYiazK5SGyy kYjNgnfNjkCfGHYCaxoBsKTuaD2YW4uU4qEXJ5yuWqDUDe9csUkyHSJZzSu3KKepTEEK ypjAxK8c6+EOBJN5LZ7mVombOP5gNXfYPyZDdEfYBwKVkSfYJgchPfPlgPfAc8j4tlkJ ncaBacHGeJdznWz8mpjBiCuwGR1SakMZS5Rka6FStmjGAZHVoZlowuxAwcDOOq7HCyWt EGMZ+yvrgT7TrT1DOdBkj6QhKey7UbmJFOCjeLa9/hcwZ5O73SFMt1c47eQUV/B84FZx 0QHQ==; darn=postgresql.org ARC-Authentication-Results: i=1; mx.google.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jeltef.nl; s=google; t=1780473847; x=1781078647; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=72xThpgFP8Ph64tij2zcAcFdlltZXe4bLTNOjXfOcbo=; b=Ew8pl7D1805cuuXHCloctSL/zAes9e0NUlxsSFHy4HtH55AH/okTP8EDajG3qb8VOf dfXsUEtaTNvLS6X4ldKDwfkF/CbfW6YJGVinsJhGM5tzsvrw26+oxFzCGgyyd0dOHuG9 weoJv/zTjKv8V07ovum/M/qnakO4UQ9iEPt934oB4EYKONIepBO5JoeVmNc0c96GKqOa EGo7623n5ZtcbBIrVsDfTUfxRxl47STc6G62AwDis7aD9Sl8Ba+9/5c5TVfU+LFZ0YSx js0hUSx+V0ASFsqjhOBM+BaknLqxgm3/rTKNtbKAiYXBlku1bEA+ma3dbdmFRCoCRrrM TxRw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1780473847; x=1781078647; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=72xThpgFP8Ph64tij2zcAcFdlltZXe4bLTNOjXfOcbo=; b=j2BHz8HCBu8sZf5WMKXEqW/nf/QPl4H+HqKqi9HZFa3jEmJ/xe4dtV9NkPrf3auCjb l+5b5ES1AuAS/CXfskRqKkZwb3shlufpLhHiUuwPuIvM1DrCl2mXAjAx/jIf3Xn0yVGw lNEX6j6sY+n20BNgz+0EJtJ0bHX4fkRGYkfo5sSrYBThjUQR1SnUaQ96t6yInIZruyb6 kkTP5j7u3gaXs82TD26m8B6g8uuzPJZEoh/Y90FTvyW9HrMBM3xZcPH5cAWKN5uaor6+ CfUqWGHBnp/BWzrojE4hXlmD+zUUjJIOmJTwYJmGt7SfKxeaBETOmqGfoDlfAgjM3Gle dJ+g== X-Forwarded-Encrypted: i=1; AFNElJ80Lf6b8XoyMD/VS54bEi13+N6JDW6es3XDmfhRxMW8CaeC3mT1wnhnzUrS2cJvPbCUK8IiMDJDrBAaWjde@postgresql.org X-Gm-Message-State: AOJu0YwK0ZFMuLrDUeHxlCdJWmqZ0VVvKyYseOTZ0a2/ob+x4myOYA4h XclMHgidBC6Ik6gmyCkpUNjJsiNAn4iifE3uQWQsU+KPM5A6zXJ8valEm7uSaYC5idT2CS2n62I VzzE58QWiN+VHZuC0MkjeYHH3kp0Nnrbc9zTU4C+8R5Tm0ARlKmEO X-Gm-Gg: Acq92OHBMPTC+j8SFkCvJP0QjIwH3LQriZABXC7mFr/ns80wXtgwNo+FNFeEdpNEFwR SZhh7U8hgz+3cU6Qou9QobyjQSBCWB+5xBuBYBpQxoNJmnSIdSnYE66CG/bEd4/Y8ywDH66Zg8b +jfzoaubnGmtShOrHm6XqGNrB5s/8HjHlWUCaFITkHfdkrWpvy8PA1nCg3BNWQNTD++PzIQmevK bB4urJZmLmBMJ1lYDo9NRcT/MoWcBNq3DidFXZDb6oAQyhW76tLklVUBsJ4lySxsN8hf8IUQ1W5 jK7SibUhbeVrpHYyMmQV X-Received: by 2002:a05:6512:800f:10b0:5a3:ff6b:cb5d with SMTP id 2adb3069b0e04-5aa7c065bb0mr500193e87.19.1780473846964; Wed, 03 Jun 2026 01:04:06 -0700 (PDT) MIME-Version: 1.0 References: <3604190.1771878013@sss.pgh.pa.us> In-Reply-To: From: Jelte Fennema-Nio Date: Wed, 3 Jun 2026 10:03:55 +0200 X-Gm-Features: AVHnY4I9Cgk8IvgR_ne1zo6_AIcywVLrZd5QEsKhb-HOYQ-fQ9lVW3G1aKZ_Kxc Message-ID: Subject: Re: PSA: Planning to grease protocol connections during 19beta To: Jacob Champion Cc: Tom Lane , PostgreSQL Hackers Content-Type: multipart/alternative; boundary="0000000000002e32e3065354dfc3" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000002e32e3065354dfc3 Content-Type: text/plain; charset="UTF-8" On Mon, Apr 13, 2026, 20:58 Jacob Champion 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 --0000000000002e32e3065354dfc3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Mon, Apr 13, 2026, 20:58 Jacob Champion <jacob.champion@enterprisedb.com> wrote:= =C2=A0
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 th= ink it'd be good if they notify us too. So we can get a sense of whethe= r it's "safe enough" to bump the protocol version at some poi= nt and/or we can bug important offenders that we have some sway over. How a= bout 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 a= n example:

Subject: [grease] ExampleProxy fails grease check
Body:
I'm using ExampleProxy and it's f= ailing the grease check. I've reported the issue upstream at https://example.com/issues/1234