| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
| Cc: | Russell Smith <mr-russ(at)pws(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Auto Vacuum |
| Date: | 2004-11-30 03:21:58 |
| Message-ID: | 200411300321.iAU3LwW14101@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Matthew T. O'Connor wrote:
> Bruce Momjian wrote:
>
> >Matthew T. O'Connor wrote:
> >
> >
> >>Bruce Momjian wrote:
> >>
> >>
> >>>I have added an auto-vacuum TODO item:
> >>>
> >>>* Auto-vacuum
> >>> o Move into the backend code
> >>> o Scan the buffer cache to find free space or use background writer
> >>> o Use free-space map information to guide refilling
> >>>
> >>>
> >>I'm not sure what you mean exactly by "Scan the buffer cache to find
> >>free space or use background writer", the other two are definitely high
> >>priority todo items (at least as far as autovacuum in concerned).
> >>
> >>
> >
> >I am thinking we could look for expired tuples when while they are in
> >the buffer cache or before they are written to disk so we don't have to
> >a sequential scan to find them.
> >
> >
>
> Is that related to autovacuum? Or is that a potential feature inside the
> actual vacuum command?
That could be part of auto-vacuum. Vacuum itself would still sequential
scan, I think. The idea is to easily grab expire tuples when they are
most cheaply found.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-11-30 03:25:08 | Re: multiline CSV fields |
| Previous Message | Matthew T. O'Connor | 2004-11-30 03:14:10 | Re: Auto Vacuum |