Horton

Re: Move un-parenthesized syntax docs to "compatibility" for few SQL commands

Nathan Bossart <nathandbossart@gmail.com>

View thread View on postgr.es
From: Nathan Bossart <nathandbossart@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>, Tom Lane <tgl@sss.pgh.pa.us>
Date: 2023-05-16T15:40:12Z
Lists: pgsql-hackers 
On Tue, May 16, 2023 at 03:28:17PM +0900, Michael Paquier wrote:
> Hmm.  This is older than the oldest version we have to support for
> pg_upgrade and co.  Would it be worth switching clusterdb to use the
> parenthesized grammar, adding on the way a test for this new grammar
> flavor without a table in the TAP tests (too costly for the main
> regression test suite)?

Since all currently-supported versions require a table name for the
parenthesized syntax, this would cause v17's clusterdb to fail on older
servers when no table name is specified.  That seems like a deal-breaker to
me.

-- 
Nathan Bossart
Amazon Web Services: https://aws.amazon.com

Commits

  1. Doc: move unparenthesized syntaxes for a few commands.

  2. Support parenthesized syntax for CLUSTER without a table name.