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
Views: Raw Message | Whole Thread | Download mbox | Resend email
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

Browse pgsql-performance by date

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