From: | Christopher Browne <cbbrowne(at)acm(dot)org> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Automatic free space map filling |
Date: | 2006-03-04 02:53:47 |
Message-ID: | 871wxiq5s4.fsf@wolfe.cbbrowne.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Centuries ago, Nostradamus foresaw when ZeugswetterA(at)spardat(dot)at ("Zeugswetter Andreas DCP SD") would write:
>> > But what about index clearing? When do you scan each index?
>>
>> At the end of each iteration (or earlier, depending on
>> maintenance_work_mem). So for each iteration you would need
>> to scan the indexes.
>>
>> Maybe we could make maintenance_work_mem be the deciding
>> factor; after scanning the indexes, do the release/reacquire
>> locks cycle.
>
> But you could do the indexes first and remember how far you can
> vacuum the heap later.
But the indexes _can't_ be done first; you _first_ need to know which
tuples are dead, which requires looking at the table itself.
--
select 'cbbrowne' || '@' || 'gmail.com';
http://linuxdatabases.info/info/languages.html
Pound for pound, the amoeba is the most vicious animal on earth.
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Fuhr | 2006-03-04 03:00:19 | Re: ACCESS EXCLUSIVE LOCK |
Previous Message | Christopher Browne | 2006-03-04 02:50:45 | Re: PostgreSQL Anniversary Summit, Call for Contributions |