Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Vacuum time degrading
- From: Wes <wespvp(at)syntegra(dot)com>
- To: Postgresql-General <pgsql-general(at)postgresql(dot)org>
- Subject: Vacuum time degrading
- Date: Mon, 28 Feb 2005 17:02:04 -0600
- Message-id: <BE48FF0C.7C01%wespvp@syntegra.com> <text/plain>
We've been doing a vacuum every night. With about 254 million rows, it was taking abut 0.8 hours. Now a few months later with about 456 million rows it is taking 4.8 hours. I did check the archives and didn't find anything like this. Why is the vacuum time not going up linearly? Since vacuum has to sequentially read the entire database, I would have expected a linear increase - about 1.5 hours now. There are currently no deletes or modifies to the database - only inserts. This is on PostgreSQL 7.4.5, RedHat ES 3.0. Wes
- Prev by Date: vacuum_cost_delay & VACUUM holding locks on GIST indexes
- Next by Date: invalid multibyte character for locale
- Previous by thread: vacuum_cost_delay & VACUUM holding locks on GIST indexes
- Next by thread: invalid multibyte character for locale
- Indexes: