From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: [HACKERS] Trivial patch to double vacuum speed on tables with no indexes |
Date: | 2006-08-27 17:12:31 |
Message-ID: | 1540.1156698751@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Gregory Stark <stark(at)enterprisedb(dot)com> writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>> How often does that case come up in the real world, for tables that are
>> large enough that you'd care about vacuum performance?
> I would have had the same objection if it resulted in substantially more
> complex code but it was so simple that it doesn't seem like a concern.
The reason the patch is so short is that it's a kluge. If we really
cared about supporting this case, more wide-ranging changes would be
needed (eg, there's no need to eat maintenance_work_mem worth of RAM
for the dead-TIDs array); and a decent respect to the opinions of
mankind would require some attention to updating the header comments
and function descriptions, too.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2006-08-27 17:40:48 | Re: integration of pgcluster into postgresql |
Previous Message | Peter Eisentraut | 2006-08-27 17:07:39 | Re: integration of pgcluster into postgresql |
From | Date | Subject | |
---|---|---|---|
Next Message | Sven Suursoho | 2006-08-27 18:36:41 | Re: plpython improvements |
Previous Message | Gregory Stark | 2006-08-27 17:00:15 | Re: Trivial patch to double vacuum speed on tables with no indexes |