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.94.2) (envelope-from ) id 1rh9zd-009vMA-S1 for pgsql-www@arkaria.postgresql.org; Mon, 04 Mar 2024 15:12:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rh9zc-008jX5-9A for pgsql-www@arkaria.postgresql.org; Mon, 04 Mar 2024 15:12:40 +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.94.2) (envelope-from ) id 1rh9zc-008jWx-2U for pgsql-www@lists.postgresql.org; Mon, 04 Mar 2024 15:12:40 +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.94.2) (envelope-from ) id 1rh9zY-002odc-G9 for pgsql-www@postgresql.org; Mon, 04 Mar 2024 15:12:39 +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 424FCWPX3597696; Mon, 4 Mar 2024 10:12:32 -0500 From: Tom Lane To: "Euler Taveira" cc: "Daniel Gustafsson" , "Marcos Pegoraro" , "Alvaro Herrera" , pgsql-www@postgresql.org Subject: Re: Diff of this page with other version In-reply-to: References: <202403021444.yyabqn4eatpx@alvherre.pgsql> Comments: In-reply-to "Euler Taveira" message dated "Mon, 04 Mar 2024 11:45:38 -0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3597694.1709565152.1@sss.pgh.pa.us> Date: Mon, 04 Mar 2024 10:12:32 -0500 Message-ID: <3597695.1709565152@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk "Euler Taveira" writes: > There is also tools like pgPedia [1] that provides a command / function > history. Unless there is a way to automate this request as Alvaro said, it > would impose extra work by adding tags to mark that a feature adds a keyword > and/or value. What happen if a deprecated keyword / value was removed? The > synopsis content can be rearranged too. I have a gut feeling that some work > should be done manually. There's no doubt that we could get *better* results with the addition of manual effort. But even htmldiff as it stands today produces *usable* results (I tried it on a couple of versions of the COPY reference page). Given that we've not offered something like this at all before, I think it's silly to put in a lot of up-front effort in advance of seeing what the demand really is. In any case, I concur with the other committers that there is simply no way we're going to accept manual change markup as an additional expectation for documentation commits. It's hard enough already. regards, tom lane