| From: | "Gaetano Mendola" <mendola(at)bigfoot(dot)com> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Vacuum full hang |
| Date: | 2003-02-02 13:33:50 |
| Message-ID: | b1j6nr$2tbu$1@news.hub.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
<mallah(at)trade-india(dot)com> wrote in message
news:8162(dot)203(dot)122(dot)61(dot)30(dot)1044192306(dot)squirrel(at)mail(dot)trade-india(dot)com(dot)(dot)(dot)
>
>
> Hmm. VACUUM FULL is supposed to do that only i guess.
>
> since version 7.2 ordinary VACUUM does not locks the table.
> and VACUUM can be performed on a live system.
>
> VACUUM FULL does the disk space reclaimation and is supposed to lock
> table to prevent updates.
>
> i guess you can do a VACUUM ANALYZE on the table instead.
>
> regds
> Mallah.
Your guess is wrong, in my case the vacuum analyze is not enough, I have a
lot
of space wasted in my HD, I need a vacuum analyze and I don't care if some
process
during the vacuum hang ( just during the vacuum operation ) but here the
strange is
that also the "vacuum" hang.
Ciao
Gaetano
| From | Date | Subject | |
|---|---|---|---|
| Next Message | mallah | 2003-02-02 13:41:19 | Re: Vacuum full hang |
| Previous Message | mallah | 2003-02-02 13:25:06 | Re: Vacuum full hang |