Re: 9.2.1 & index-only scans : abnormal heap fetches after VACUUM FULL
От | Bruce Momjian |
---|---|
Тема | Re: 9.2.1 & index-only scans : abnormal heap fetches after VACUUM FULL |
Дата | |
Msg-id | 20131203193410.GJ27105@momjian.us обсуждение исходный текст |
Ответ на | Re: 9.2.1 & index-only scans : abnormal heap fetches after VACUUM FULL (Robert Haas <robertmhaas@gmail.com>) |
Список | pgsql-hackers |
On Tue, Dec 3, 2013 at 02:01:52PM -0500, Robert Haas wrote: > On Tue, Dec 3, 2013 at 11:25 AM, Bruce Momjian <bruce@momjian.us> wrote: > > On Thu, Nov 28, 2013 at 05:38:05PM -0500, Bruce Momjian wrote: > >> > I wonder if we ought to mark each page as all-visible in > >> > raw_heap_insert() when we first initialize it, and then clear the flag > >> > when we come across a tuple that isn't all-visible. We could try to > >> > set hint bits on the tuple before placing it on the page, too, though > >> > I'm not sure of the details. > >> > >> I went with the per-page approach because I wanted to re-use the vacuum > >> lazy function. Is there some other code that does this already? I am > >> trying to avoid yet-another set of routines that would need to be > >> maintained or could be buggy. This hit bit setting is tricky. > >> > >> And thanks much for the review! > > > > So, should I put this in the next commit fest? > > +1. OK, I added it to the January commit fest. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + Everyone has their own god. +
В списке pgsql-hackers по дате отправления: