| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Time to remove unparenthesized syntax for VACUUM? |
| Date: | 2022-07-02 01:45:53 |
| Message-ID: | 20220702014553.GB2301877@rfd.leadboat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jul 01, 2022 at 03:13:16PM -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.
Deprecation doesn't imply eventual removal. java.io.StringBufferInputStream
has been deprecated for 25 years. One should not expect it or the old VACUUM
syntax to go away.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2022-07-02 03:17:17 | Re: pg15b2: large objects lost on upgrade |
| Previous Message | Noah Misch | 2022-07-02 01:21:28 | Re: First draft of the PG 15 release notes |