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

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
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-05-16 15:40:12
Message-ID: 20230516154012.GA3087879@nathanxps13
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Lakhin 2023-05-16 16:00:00 Re: Order changes in PG16 since ICU introduction
Previous Message Kirk Wolak 2023-05-16 15:33:47 Re: Adding SHOW CREATE TABLE