Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

Re: Database size Vs performance degradation


  • From: Andrzej Zawadzki <zawadaa(at)wp(dot)pl>
  • To: pgsql-performance(at)postgresql(dot)org
  • Subject: Re: Database size Vs performance degradation
  • Date: Thu, 31 Jul 2008 19:49:28 +0200
  • Message-id: <4891FB28.7000800@wp.pl> <text/plain>

Mark Roberts wrote:
On Wed, 2008-07-30 at 13:51 -0400, Tom Lane wrote:
Huh?  Vacuum doesn't block writes.

                        regards, tom lane


Of course, you are correct.  I was thinking of Vacuum full, which is
recommended for use when you're deleting the majority of rows in a
table.

http://www.postgresql.org/docs/8.1/interactive/sql-vacuum.html
Maybe I'm wrong but if this "bulk insert and delete" process is cyclical then You don't need vacuum full. Released tuples will fill up again with fresh data next day - after regular vacuum.

I have such situation at work. Size of database on disk is 60GB and is stable.

--
Andrzej Zawadzki



Home | Main Index | Thread Index

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group