public inbox for [email protected]  

help / color / mirror / Atom feed

From: Jacob Champion <[email protected]>
To: PostgreSQL Hackers <[email protected]>
Cc: Jelte Fennema-Nio <[email protected]>
Subject: Re: PSA: Planning to grease protocol connections during 19beta
Date: Mon, 23 Feb 2026 12:00:49 -0800
Message-ID: <CAOYmi+kVfqgPAaR1QuY7=RPBYR6MsA3V3_f5+H-75uC06YCDDA@mail.gmail.com> (raw)
In-Reply-To: <CAOYmi+kqt_gn-wvUjJG1j3MM4LDDsRMURSPz2eMxfABu0iGtpw@mail.gmail.com>
References: <CAOYmi+kqt_gn-wvUjJG1j3MM4LDDsRMURSPz2eMxfABu0iGtpw@mail.gmail.com>

On Tue, Dec 9, 2025 at 5:16 PM Jacob Champion
<[email protected]> wrote:
> I want to make sure this doesn't take anyone by surprise: I'm planning
> to get Jelte's "grease" patch into shape for a commit some time in
> January.

As of January 54th, this is committed.

I wanted to get people's thoughts on communication. As it stands now,
beta users will be directed towards our own documentation [1] when
they hit a grease failure. But personally, I'd like the landing page
to be on the wiki, for several reasons:

- It can be written in a more casual voice, and go into detail that
would be out of place in a docs note
- It's easier to change quickly in response to end user feedback, if
we receive any
- It can remain in place after the beta period ends

But having libpq link to a wiki page makes that page a vandalism
target. Can a wiki page be protected in a way that still lets
committers edit it? Is there a third option that works better than the
docs or the wiki?

--Jacob

[1] https://www.postgresql.org/docs/devel/libpq-connect.html#LIBPQ-CONNECT-MAX-PROTOCOL-VERSION

view thread (9+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: PSA: Planning to grease protocol connections during 19beta
  In-Reply-To: <CAOYmi+kVfqgPAaR1QuY7=RPBYR6MsA3V3_f5+H-75uC06YCDDA@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox