| From: | "Adam Erickson" <adamre(at)cox(dot)net> |
|---|---|
| To: | <pgsql-novice(at)postgresql(dot)org> |
| Subject: | Re: Answering my own question |
| Date: | 2002-05-16 15:56:46 |
| Message-ID: | ALEKKHACBIAEBNBPFKPCAEJCCOAA.adamre@cox.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
> As in another post, VACUUM ANALYZE has fixed my index, optimer, query plan
> problem.
>
> A follow-up question I have is about VACUUM FULL.
>
> There's no mention of "FULL" as an arguement to VACUUM in the 7.1.3
> doc/html on-line reference manual. Was FULL added to a later release?
The changed vacuum in 7.[something]. Among other things, which I am unaware
of, vacuum no longer frees physical disk space when cleaning up tables.
Instead, it frees space in the file for pg to reuse. VACUUM FULL was then
added for those who wanted vacuum to behave as it did before.
One nice thing about the new behavior is that it no longer needs to lock the
tables during vacuum. Doing a vacuum full will lock the table though.
-Adam
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2002-05-16 16:06:23 | Re: Casting from varchar to numeric |
| Previous Message | Tom Ansley | 2002-05-16 15:48:47 | Casting from varchar to numeric |