From: | Joseph Shraibman <jks(at)selectacast(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Idea for vacuuming |
Date: | 2006-06-23 18:00:38 |
Message-ID: | e7ha83$1dav$1@news.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I like to make sure the vacuum takes place during off peak times, which
is why I don't use autovacuum.
Jim Nasby wrote:
> 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
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>
From | Date | Subject | |
---|---|---|---|
Next Message | TJ O'Donnell | 2006-06-23 18:14:15 | Re: Changing encoding of a database |
Previous Message | Dylan Hansen | 2006-06-23 17:43:06 | pg_dump With OIDs Supported? |