We're using Postgresql 8.3.7 on Debian. We are seeing a very strange performance situation with our application which I am
hoping that someone can shed light on.
Our tests find that our application runs quite well on 8.3.7 initially. The test consists of database creation followed by 30
cycles of creation and removal of approximately 1,000,000 rows (across all tables) per cycle. However, when database
maintenance takes place (which consists of a VACUUM FULL operation, and some table REINDEX operations), subsequent cycle
performance is more than 2x worse. What's more, after one VACUUM FULL operation has been done on the database, no subsequent
VACUUM FULL operations *ever* seem to restore it to proper performance levels.
We used the same general maintenance procedure with 8.2 and found that it worked as expected, so we were quite surprised to
discover this problem with 8.3.7. Anybody know what's going on?
350 Massachusetts Avenue, 4th Floor, Cambridge, MA 02139 USA
Where to find it.
This message may contain privileged, proprietary, and otherwise private
information. If you are not the intended recipient, please notify the
pgsql-performance by date
|Next:||From: Robert Haas||Date: 2009-09-18 13:40:22|
|Subject: Re: Database performance post-VACUUM FULL|
|Previous:||From: Hell, Robert||Date: 2009-09-18 09:50:08|
|Subject: Re: Different query plans for the same query|