| From: | Melanie Plageman <melanieplageman(at)gmail(dot)com> |
|---|---|
| To: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Move un-parenthesized syntax docs to "compatibility" for few SQL commands |
| Date: | 2023-04-21 22:29:16 |
| Message-ID: | CAAKRu_bc5uHieG1976kGqJKxyWtyQt9yvktjsVX+i7NOigDjOA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
I find the inclusion of the un-parenthesized syntax for VACUUM, ANALYZE,
and EXPLAIN in the docs makes it harder to understand the preferred,
parenthesized syntax (see [1] as an example).
Over in [2], it was suggested that moving the un-parenthesized syntax to
the "Compatibility" section of their respective docs pages would be
okay. Patch attached.
I left out CLUSTER since that syntax change is so new.
- Melanie
[1] https://www.postgresql.org/docs/devel/sql-analyze.html
[2] https://www.postgresql.org/message-id/3024596.1681940741%40sss.pgh.pa.us
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Doc-Move-un-parenthesized-syntax-to-compatibility.patch | text/x-patch | 3.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Regina Obe | 2023-04-21 22:39:26 | RE: Order changes in PG16 since ICU introduction |
| Previous Message | Jeff Davis | 2023-04-21 21:56:19 | Re: Order changes in PG16 since ICU introduction |