Pavan Deolasee wrote:
> On 7/23/07, Alvaro Herrera <alvherre@commandprompt.com> wrote:
>> Certainly it doesn't prevent starvation completely -- really there is no
>> way to completely prevent starvation unless you have as many workers as
>> you have tables, and one disk for each. What DSM does do is let the big
>> tables be vacuumed quickly which makes most of the problem go away.
>
> Frankly I haven't seen DSM results very closely, but DSM can help
> us avoid full heap scans (and thats a big thing!), but it can't avoid the
> associated index scans and that might limit our ability to vacuum very
> large tables frequently.
I haven't seen DSM either so IMBFoS. You are right about index scans
though. Fortunately they are not as expensive as they used to be thanks
to Heikki's changes to allow physical order scanning.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
