From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | mlw <markw(at)mohawksoft(dot)com> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Name for new VACUUM |
Date: | 2001-08-02 23:51:31 |
Message-ID: | 14815.996796291@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
mlw <markw(at)mohawksoft(dot)com> writes:
> Why rename VACUUM, why not create a new command RECLAIM, or something like
> that. RECLAIM does the VACUUM NOLOCK, while vacuum does the locking.
Um, that gets the default backwards IMHO, where "default" = "what
existing scripts will do".
> The term RECLAIM will make more sense to new comers than VACUUM,
What's your basis for claiming that?
In any case, VACUUM is the term already used in all our documentation.
I have no appetite for trying to teach people and documents that
currently know "you must do VACUUM periodically" that the new truth is
"you must do VACUUM or RECLAIM periodically". All these discussions
about which should be default aside, the bottom line is that the two
pieces of code do more-or-less the same thing from a high level
perspective. Calling them completely different names isn't going to
make things easier for novices. Calling them different options of the
same statement seems like the right thing to me.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Fernando Nasser | 2001-08-02 23:58:25 | Re: Revised Patch to allow multiple table locks in "Unison" |
Previous Message | mlw | 2001-08-02 23:48:21 | Re: Name for new VACUUM |