From: | gerry(dot)smit(at)lombard(dot)ca |
---|---|
To: | "Adam Erickson" <adamre(at)cox(dot)net> |
Cc: | pgsql-novice(at)postgresql(dot)org, pgsql-novice-owner(at)postgresql(dot)org |
Subject: | Re: Answering my own question |
Date: | 2002-05-16 17:13:22 |
Message-ID: | OFC6AE50E2.0608812A-ON85256BBB.005E917D@lombard.ca |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
VACUUM FULL is NOT available in 7.1.3, so it must be later.
Gerry
"Adam Erickson"
<adamre(at)cox(dot)net> To: pgsql-novice(at)postgresql(dot)org
Sent by: cc:
pgsql-novice-owner(at)pos Fax to:
tgresql.org Subject: Re: [NOVICE] Answering my own question
16/05/2002 11:56 AM
> 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
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
From | Date | Subject | |
---|---|---|---|
Next Message | gerry.smit | 2002-05-16 17:17:35 | Re: Trouble with index in 7.1 |
Previous Message | Adam Erickson | 2002-05-16 16:38:21 | Re: Casting from varchar to numeric |