Re: Time to remove unparenthesized syntax for VACUUM? - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Time to remove unparenthesized syntax for VACUUM?
Date
Msg-id 20220701221928.flg6rbcilub7czij@alap3.anarazel.de
Whole thread Raw
In response to Re: Time to remove unparenthesized syntax for VACUUM?  (Nathan Bossart <nathandbossart@gmail.com>)
Responses Re: Time to remove unparenthesized syntax for VACUUM?
List pgsql-hackers
Hi,

On 2022-07-01 15:13:16 -0700, Nathan Bossart wrote:
> On Fri, Jul 01, 2022 at 03:05:55PM -0700, Andres Freund wrote:
> > On 2022-07-01 14:56:42 -0700, Nathan Bossart wrote:
> >> The unparenthesized syntax for VACUUM has been marked deprecated since v9.1
> >> (ad44d50).  Should it be removed in v16?  If not, should we start emitting
> >> WARNINGs when it is used?
> > 
> > What would we gain? ISTM that the number of scripts and typing habits that'd
> > be broken would vastly exceed the benefit.
> 
> Beyond removing a few lines from gram.y and vacuum.sgml, probably not much.
> If it isn't going to be removed, IMO we should consider removing the
> deprecation notice in the docs.

Still serves as an explanation as to why newer options haven't been / won't be
added in an unparenthesized manner. And maybe there one day will be reason to
remove them, e.g. grammar ambiguities.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: EINTR in ftruncate()
Next
From: Nathan Bossart
Date:
Subject: Re: Time to remove unparenthesized syntax for VACUUM?