| From: | Florents Tselai <florents(dot)tselai(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | doc: guidance on SQL/JSON functions vs jsonpath operators |
| Date: | 2026-02-02 16:15:00 |
| Message-ID: | CA+v5N40ChG-vgY_WeNKPdVWgAhn=BwBbT=HCuO0QUGW79W_w7g@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
While reading the docs for the SQL/JSON functions added in 17,
I noticed that the current text provides no guidance on when to prefer
these new functions over the existing jsonpath operators.
I was thinking of something like the attached patch,
which introduces a Tip and a Note to clarify the distinction
(focusing on portability/error-handling vs. conciseness/indexing).
PS: Tbh, the documentation around these PG17 additions is currently quite
dense. It likely needs more comprehensive content - which I may provide
soon - but this seemed like an obvious first step.
| Attachment | Content-Type | Size |
|---|---|---|
| doc-sqljson-jsonpath.patch | application/octet-stream | 2.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Jones | 2026-02-02 16:17:13 | Re: display hot standby state in psql prompt |
| Previous Message | Lukas Fittl | 2026-02-02 16:11:32 | Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc? |