Re: VACUUM DATABASE - Mailing list pgsql-hackers

From Tom Lane
Subject Re: VACUUM DATABASE
Date
Msg-id 20973.1122433651@sss.pgh.pa.us
Whole thread Raw
In response to VACUUM DATABASE  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
Simon Riggs <simon@2ndquadrant.com> writes:
> I'd like to suggest altering the syntax of VACUUM so that it is possible
> to issue the command VACUUM DATABASE. The keyword DATABASE would be
> optional, to allow backward compatibility.

This would require converting DATABASE from an unreserved keyword into
a fully reserved keyword (else the parser couldn't tell whether you
were asking for a vacuum of a single table named "database").  That
seems to me like a change moderately likely to break existing
applications ... not that I'd ever name a table, column, function,
type, or schema "database", but I'll bet somebody out there has.

I don't really see the argument that "let's make life easier for people
who didn't read the manual" trumps "let's not break applications that
chose legitimate object names".

Perhaps we need some work on the documentation instead...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Michael Glaesemann
Date:
Subject: Re: Couple of minor buildfarm issues
Next
From: Andrew Dunstan
Date:
Subject: Re: Couple of minor buildfarm issues