Re: Move un-parenthesized syntax docs to "compatibility" for few SQL commands - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: Move un-parenthesized syntax docs to "compatibility" for few SQL commands
Date
Msg-id 20230516154012.GA3087879@nathanxps13
Whole thread Raw
In response to Re: Move un-parenthesized syntax docs to "compatibility" for few SQL commands  (Michael Paquier <michael@paquier.xyz>)
List 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



pgsql-hackers by date:

Previous
From: Kirk Wolak
Date:
Subject: Re: Adding SHOW CREATE TABLE
Next
From: Alexander Lakhin
Date:
Subject: Re: Order changes in PG16 since ICU introduction