From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: VACUUM DATABASE |
Date: | 2005-07-27 03:07:31 |
Message-ID: | 20973.1122433651@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Simon Riggs <simon(at)2ndquadrant(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2005-07-27 03:13:19 | Re: Couple of minor buildfarm issues |
Previous Message | Andrew Dunstan | 2005-07-27 03:06:50 | Re: Couple of minor buildfarm issues |