| From: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
| Subject: | Re: PSA: Planning to grease protocol connections during 19beta |
| Date: | 2026-02-23 20:00:49 |
| Message-ID: | CAOYmi+kVfqgPAaR1QuY7=RPBYR6MsA3V3_f5+H-75uC06YCDDA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Dec 9, 2025 at 5:16 PM Jacob Champion
<jacob(dot)champion(at)enterprisedb(dot)com> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2026-02-23 20:14:42 | Re: AIX support |
| Previous Message | Jacob Champion | 2026-02-23 19:57:46 | Re: libpq: Bump protocol version to version 3.2 at least until the first/second beta |