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 1wMSQB-0006eZ-2g for pgsql-hackers@arkaria.postgresql.org; Mon, 11 May 2026 15:19:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wMSQA-001SQr-1s for pgsql-hackers@arkaria.postgresql.org; Mon, 11 May 2026 15:19:50 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wMSQA-001SQj-0v for pgsql-hackers@lists.postgresql.org; Mon, 11 May 2026 15:19:50 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wMSQ7-0000000048w-3HG3 for pgsql-hackers@postgresql.org; Mon, 11 May 2026 15:19:50 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.18.1/8.18.1) with ESMTP id 64BFJiQW2077215; Mon, 11 May 2026 11:19:44 -0400 From: Tom Lane To: Marcos Pegoraro cc: Michael Paquier , pgsql-hackers Subject: Re: Missing jsonb_ ... functions on DOCs In-reply-to: References: Comments: In-reply-to Marcos Pegoraro message dated "Mon, 11 May 2026 12:07:33 -0300" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <2077213.1778512784.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Mon, 11 May 2026 11:19:44 -0400 Message-ID: <2077214.1778512784@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Marcos Pegoraro writes: > Em dom., 10 de mai. de 2026 às 23:08, Michael Paquier > escreveu: >> Well, it seems to me that the intention is that it is pointless to >> document the functions because that the users need only to be aware of >> the operators, and the operators are enough to manipulate the jsonb >> blobs. Documenting the functions would be just duplicating what we >> already have for the operators, as listed here: >> https://www.postgresql.org/docs/devel/functions-json.html > A function is self explanatory, an operator is not. We have a general policy of not documenting functions that underlie operators, simply because doing otherwise would bloat the documentation enormously while not adding much value. Do we really need documentation entries for int4pl, int48gt, float84mul, etc etc etc? I'm sure there are a few places where that policy wasn't followed for some reason, but I'm loath to abandon it. There are circa 800 entries in pg_operator (and that's just for the core code). regards, tom lane