Re: Missing jsonb_ ... functions on DOCs

From: Marcos Pegoraro <marcos(at)f10(dot)com(dot)br>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Missing jsonb_ ... functions on DOCs
Date: 2026-05-12 21:45:05
Message-ID: CAB-JLwbjNS-4qYGCt-EZgvR+edcuLNrzDOsT+tCT6T3ZCmtPqQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Em seg., 11 de mai. de 2026 às 12:19, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> escreveu:

> 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.
>

And if we have a separate page containing all non documented functions
related to their correspondent operators ?
Just one page with one table with all undocumented jsonb functions, another
table with undocumented interval functions and so on.

This way we document them and all main pages are not bloated with
duplicated functions.
We need only a "Click here to see the functions corresponding to the
operators you see in this table.", or something

What do you think ?

regards
Marcos

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Zsolt Parragi 2026-05-12 21:48:20 Re: Add ssl_(supported|shared)_groups to sslinfo
Previous Message Tom Lane 2026-05-12 21:33:50 Re: pgindent versus struct members and typedefs