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 1rwoUs-004LO0-VG for pgsql-hackers@arkaria.postgresql.org; Tue, 16 Apr 2024 19:29:38 +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 1rwoUq-005pUc-8R for pgsql-hackers@arkaria.postgresql.org; Tue, 16 Apr 2024 19:29:36 +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 1rwoUp-005pUU-TX for pgsql-hackers@lists.postgresql.org; Tue, 16 Apr 2024 19:29:35 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rwoUn-003BCA-DJ for pgsql-hackers@postgresql.org; Tue, 16 Apr 2024 19:29:34 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2024011501; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=ufuqqxxTJJi02mi2x3CDiozvutuUHsVK86QeYdUDDBw=; b=Q+BDb SLboHQsplcj3VsMeKJOS/cHshvTNC8cAX4KzbewlRz4M/43EEr/PpW1WoIUy2/CpjtSKDb47t0JCH poDr2Iy/vMHzJDn1R9DPXfR5fMQunUkuWI8SH079Cs1JOLVjcqi51JvPmktrWQRQWvVYaRKXNLg5Q vy1/EBtPh8Lp1jYt/4GD3aGrNMNKFI1fE9TNSORP0H2u337jNEwQGgbVO45jMKNwNtR5ZURJTWLpM 5W5HNSzBymYm8xA2jgxLsIk7hwtShuyf7GySM1l+nP48yXzXjwOikhMBdMgepgDEcbAcdyFR5ETd7 MlEq2pB/MV115d03/CkeznkNFSYMQ==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1rwoUj-009pf6-0Z; Tue, 16 Apr 2024 15:29:29 -0400 Date: Tue, 16 Apr 2024 15:29:29 -0400 From: Bruce Momjian To: Tom Lane Cc: Andres Freund , Andrew Dunstan , Robert Haas , "pgsql-hackers@postgresql.org" Subject: Re: documentation structure Message-ID: References: <20240416182310.2j6g5fqqcwi4s6wm@awork3.anarazel.de> <1355791.1713294332@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1355791.1713294332@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, Apr 16, 2024 at 03:05:32PM -0400, Tom Lane wrote: > Andres Freund writes: > > I think we should work on generating a lot of func.sgml. Particularly the > > signature etc should just come from pg_proc.dat, it's pointlessly painful to > > generate that by hand. And for a lot of the functions we should probably move > > the existing func.sgml comments to the description in pg_proc.dat. > > Where are you going to get the examples and text descriptions from? > (And no, I don't agree that the pg_description string should match > what's in the docs. The description string has to be a short > one-liner in just about every case.) > > This sounds to me like it would be a painful exercise with not a > lot of benefit in the end. Maybe we could _verify_ the contents of func.sgml against pg_proc. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you.