| From: | "Jim C(dot) Nasby" <decibel(at)decibel(dot)org> |
|---|---|
| To: | Christopher Browne <cbbrowne(at)acm(dot)org> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Real-Time Vacuum Possibility |
| Date: | 2005-03-21 08:04:35 |
| Message-ID: | 20050321080435.GK51784@decibel.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Mar 17, 2005 at 05:22:41AM +0000, Christopher Browne wrote:
> What strikes me as being a useful approach would be to set up an
> LRU-ordered (or perhaps unordered) queue of pages that have had tuples
> "killed off" by DELETE or UPDATE.
From http://www.postgresql.org/docs/faqs.TODO.html :
* Maintain a map of recently-expired rows
This allows vacuum to reclaim free space without requiring
a sequential scan
--
Jim C. Nasby, Database Consultant decibel(at)decibel(dot)org
Give your computer some brain candy! www.distributed.net Team #1828
Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Qingqing Zhou | 2005-03-21 09:56:44 | Prevent conflicting SET options from being set |
| Previous Message | Pavel Stehule | 2005-03-21 06:59:55 | Re: custome exception handling support ? |