From: | Jim Nasby <decibel(at)decibel(dot)org> |
---|---|
To: | Joseph Shraibman <jks(at)selectacast(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Idea for vacuuming |
Date: | 2006-06-23 05:29:23 |
Message-ID: | F6658C76-3D31-4BE7-90D2-733F652F89B3@decibel.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Jun 22, 2006, at 7:12 PM, Joseph Shraibman wrote:
> I'm running a 8.0 database. I have a very large log table that is
> rarely updated or deleted from. The nightly vacuum does not know
> this, and spends a lot of time on it, and all its indexes.
>
> My RFE: When vacuuming a table, pg should try to vacuum the primary
> key first. If that results in 0 recovered entries, then assume the
> table has no updates/deletes and skip the rest of that table. I'm
> picking the primary key here, but any index that indexes each row
> of the table will do. Maybe it should just pick the smallest index
> that indexes each row of the table.
*shrug* It's kinda hard to get excited about that when running
autovacuum (or pg_autovacuum in the case of 8.0) would be a much
better solution.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2006-06-23 05:41:07 | Re: minimizing downtime when upgrading |
Previous Message | Jim Nasby | 2006-06-23 05:25:18 | Re: Out of memory error in 8.1.0 Win32 |