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

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: 2008-07-31 17:49:28
Message-ID: 4891FB28.7000800@wp.pl (view raw or flat)
Thread:
Lists: pgsql-performance
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

In response to

Responses

pgsql-performance by date

Next:From: Scott MarloweDate: 2008-08-01 01:27:46
Subject: Re: SSD Performance Article
Previous:From: Matthew T. O'ConnorDate: 2008-07-31 17:45:38
Subject: SSD Performance Article

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group