| From: | "Shridhar Daithankar" <shridhar_daithankar(at)persistent(dot)co(dot)in> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Doubt w.r.t vacuum |
| Date: | 2003-07-28 08:59:36 |
| Message-ID: | 3F253350.12198.E86C138@localhost |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
I was just wondering over it. This is for difference between vacuum full and
vacuum analyze. Can somebody enlighten,
1. IIRC vacuum recovers/reuses dead tuples generated from update but can not do
so for delete? Why?
2. Vacuum full locks entire table, is it possible that it locks a page at a
time and deal with it. It will make vacuum full non-blocking at the cost of
letting it run for a longer time. Or is it that the defragmentation algorithm
needs more than a page?
Just a thought..
Bye
Shridhar
--
Weed's Axiom: Never ask two questions in a business letter. The reply will
discuss the one in which you are least interested and say nothing about the
other.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2003-07-28 09:10:39 | Warning for undefined cursor |
| Previous Message | Peter Eisentraut | 2003-07-28 08:36:06 | Re: Some macros for error field codes |