From: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
---|---|
To: | Bill Moran <wmoran(at)potentialtech(dot)com> |
Cc: | Rick Gigger <rick(at)alpinenetworking(dot)com>, gsstark(at)mit(dot)edu, pgsql-general(at)postgresql(dot)org |
Subject: | Re: VACUUM Question |
Date: | 2004-06-04 20:38:15 |
Message-ID: | 20040604203815.GB28030@dcc.uchile.cl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Jun 04, 2004 at 03:40:45PM -0400, Bill Moran wrote:
> Rick Gigger <rick(at)alpinenetworking(dot)com> wrote:
>
> > Does VACUUM FULL just lock entire tables and thus cause you to
> > essentially have downtime on that database because it doesn't respond
> > quickly or do you actually have to shut down postgres to safely do a
> > vacuum full?
>
> The former. You don't shut the database server down, but it won't be
> responsive while vacuum full is running.
But only for the table that's currently being vacuumed: there's only one
table locked at any time.
(A different issue is the IO storm caused by the vacuum, which makes
everything else slower.)
--
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"En las profundidades de nuestro inconsciente hay una obsesiva necesidad
de un universo lógico y coherente. Pero el universo real se halla siempre
un paso más allá de la lógica" (Irulan)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-06-04 20:57:05 | Re: VACUUM Question |
Previous Message | Dann Corbit | 2004-06-04 20:28:28 | Re: TimeOf(Subselects|Joins)FromLargeTables? |