| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Melanie Plageman <melanieplageman(at)gmail(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Move un-parenthesized syntax docs to "compatibility" for few SQL commands |
| Date: | 2023-04-21 22:55:22 |
| Message-ID: | 20230421225522.GA1445359@nathanxps13 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Apr 21, 2023 at 06:29:16PM -0400, Melanie Plageman wrote:
> 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 think that's reasonable.
> I left out CLUSTER since that syntax change is so new.
I think it'd be okay to move this one, too. The parenthesized syntax has
been available since v14, and I suspect CLUSTER isn't terribly widely used,
anyway. (Side note: it looks like "CLUSTER (VERBOSE)" doesn't work, which
seems weird to me.)
Most of these commands have an existing note about the deprecated syntax.
Could those be removed with this change?
--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2023-04-21 23:00:30 | Re: Order changes in PG16 since ICU introduction |
| Previous Message | Regina Obe | 2023-04-21 22:39:26 | RE: Order changes in PG16 since ICU introduction |