From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Michael Guerin <guerin(at)rentec(dot)com> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: vacuum full question. |
Date: | 2004-04-21 19:14:12 |
Message-ID: | 14511.1082574852@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Michael Guerin <guerin(at)rentec(dot)com> writes:
> What happens when a vacuum full is canceled? Is any of the completed
> work retained, or is everything lost?
You lose it all; in fact you are worse off than when you started,
because there is now *more* work for the next vacuum to do --- it
has to clean up the dead tuples that the canceled vacuum created
(in the process of moving data around) and never got to commit.
However, this is on a per-table basis --- if you are running a
database-wide vacuum full, it commits after each table, so the
already-processed tables are done.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Martin Atukunda | 2004-04-22 13:03:05 | comma separated value splitting |
Previous Message | Tom Lane | 2004-04-21 19:03:28 | Re: Timestamp Default value |