| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
| Subject: | Re: PSA: Planning to grease protocol connections during 19beta |
| Date: | 2026-02-23 20:20:13 |
| Message-ID: | 3604190.1771878013@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> writes:
> 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?
We have the ability to lock down a wiki page, but I believe that means
nobody can edit it until a wiki admin unlocks it. That might be the
way to go here though. I concur with your reasoning that the main
docs are a less-good place.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2026-02-23 20:26:29 | Re: Use LOCKMODE in parse_relation.c/.h |
| Previous Message | Álvaro Herrera | 2026-02-23 20:16:50 | Re: [PATCH] Add Windows support for backtrace_functions (MSVC only) |