| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Erik Rijkers <er(at)xs4all(dot)nl>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: JSON Functions and Operators Docs for v15 |
| Date: | 2022-05-16 19:33:28 |
| Message-ID: | 202205161933.dgq3s3ib4epn@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2022-May-16, Andrew Dunstan wrote:
> Thanks. I have incorporated all of these, added a result for the last
> json_table example, and done some more wordsmithing around PLAN DEFAULT.
For sure this is a big improvement, thanks. No longer do we have to
refer to section 9.16.3.2.2.3 -- that's in table 9.53 now.
I noticed that after applying it, the (some?) synopses end up partly
typeset with regular typeface rather than fixed-width, which looks a bit
odd. I think you need some <literal> tags around keywords and
<parameter> around the parameters to those; that's how
<function>overlay</function> does it for example for its
PLACING/FROM/FOR weird SQL bits.
Thanks!
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2022-05-16 20:02:37 | Re: weird comments in Memoize nodes |
| Previous Message | Erik Rijkers | 2022-05-16 19:06:59 | Re: JSON Functions and Operators Docs for v15 |