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-11 18:33:08
Message-ID: CAB-JLwZLitbYDPa8zU5=tb+9t5eXA6Cq8qE5uSEbM9=x2ebVDQ@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:

> There are circa 800 entries in pg_operator (and that's just for the core
> code).
>

It is precisely because of this number of operators that I would like to
document the functions related to them.
When you read SQL and there is an operator, you need to think, "Did I use
the right operator? I'll check the documentation to see if that's the one."
If I use a word, I have no doubt. The word Diff is completely different
than the word Equal, but the operator != is very similar to the operator =

Maybe we can find a way to have both on DOCs.
Maybe put function name just after operator definition
jsonb @> jsonb → boolean (jsonb_contains())
Maybe a tooltip on that operator.

I don't know how, but from a user's point of view, I know that not
documenting isn't the best approach.

regards
Marcos

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Antonin Houska 2026-05-11 19:30:01 Re: Adding REPACK [concurrently]
Previous Message Zsolt Parragi 2026-05-11 18:32:02 Re: [PATCH] Preserve replication origin OIDs in pg_upgrade