Search Postgresql Archives
Idea for vacuuming
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
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.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]
[Postgresql Jobs]
[Postgresql Admin]
[Postgresql Performance]
[Linux Clusters]
[PHP Home]
[PHP on Windows]
[Kernel Newbies]
[PHP Classes]
[PHP Books]
[PHP Databases]
[Postgresql & PHP]
[Yosemite]