From: | Greg Stark <gsstark(at)mit(dot)edu> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Vacuum thoughts |
Date: | 2003-10-20 16:25:29 |
Message-ID: | 87n0bvswp2.fsf@stark.dyndns.tv |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Greg Stark <gsstark(at)MIT(dot)EDU> writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>
> > You keep ignoring the problem of removing index entries. To vacuum an
> > individual page, you need to be willing to read in (and update) all
> > index pages that reference the tuples-to-be-deleted.
>
> Hm. If the visibility information were stored in the index then that could be
> postponed and done when the index page was read or when it was flushed.
Or possibly if we could reuse the space in the table without updating the
index and be able to recognize that the tuple no longer corresponded to the
index entry when we next saw the index entry.
I suspect that would take as much space to keep track of as the visibility
information though.
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Jeroen T. Vermeulen | 2003-10-20 16:59:13 | Re: In-doubt window |
Previous Message | Tom Lane | 2003-10-20 16:18:44 | Re: In-doubt window |