From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Gregory Stark <stark(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: Visibility map, partial vacuums |
Date: | 2009-01-15 15:57:09 |
Message-ID: | 496F5CD5.3010300@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian wrote:
> Heikki Linnakangas wrote:
>>>> Also, is anything being done about the concern about 'vacuum storm'
>>>> explained below?
>>> I'm interested too.
>> The additional "vacuum_freeze_table_age" (as I'm now calling it) setting
>> I discussed in a later thread should alleviate that somewhat. When a
>> table is autovacuumed, the whole table is scanned to freeze tuples if
>> it's older than vacuum_freeze_table_age, and relfrozenxid is advanced.
>> When different tables reach the autovacuum threshold at different times,
>> they will also have their relfrozenxids set to different values. And in
>> fact no anti-wraparound vacuum is needed.
>>
>> That doesn't help with read-only or insert-only tables, but that's not a
>> new problem.
>
> OK, is this targeted for 8.4?
Yes. It's been on my todo list for a long time, and I've also added it
to the Open Items list so that we don't lose track of it.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Bernd Helmle | 2009-01-15 16:04:44 | Re: FWD: Re: Updated backslash consistency patch |
Previous Message | Bruce Momjian | 2009-01-15 15:52:47 | Re: Visibility map, partial vacuums |