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 1vucPk-00G6mE-2o for pgsql-hackers@arkaria.postgresql.org; Mon, 23 Feb 2026 20:20:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vucPj-00F2Zf-2Z for pgsql-hackers@arkaria.postgresql.org; Mon, 23 Feb 2026 20:20:19 +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 1vucPj-00F2Z8-1e for pgsql-hackers@lists.postgresql.org; Mon, 23 Feb 2026 20:20:19 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1vucPg-00000000qkN-2oTk for pgsql-hackers@postgresql.org; Mon, 23 Feb 2026 20:20:18 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 61NKKDBD3604191; Mon, 23 Feb 2026 15:20:13 -0500 From: Tom Lane To: Jacob Champion cc: PostgreSQL Hackers , Jelte Fennema-Nio Subject: Re: PSA: Planning to grease protocol connections during 19beta In-reply-to: References: Comments: In-reply-to Jacob Champion message dated "Mon, 23 Feb 2026 12:00:49 -0800" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3604189.1771878013.1@sss.pgh.pa.us> Date: Mon, 23 Feb 2026 15:20:13 -0500 Message-ID: <3604190.1771878013@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Jacob Champion 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