From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | "Rafael Domiciano" <rafael(dot)domiciano(at)gmail(dot)com> |
Cc: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Tino Schwarze" <postgresql(at)tisc(dot)de>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Configuring Shared Buffers |
Date: | 2008-07-01 01:05:10 |
Message-ID: | dcc563d10806301805qfa1b99dv8763bf22a75ec693@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Updates = delete / insert
inserts only create dead tuples if they fail.
So, assuming no failed inserts, you're creating 55k dead tuples a day.
You can run vacuum verbose to get a report on how many dead tuples
your tables / database has to get an idea if you're vacuuming often
enough.
If vacuuming makes the machine too slow look at setting
vacuum_cost_delay = 10 and see if that helps. Vacuums will take
longer but won't be as intrusive.
On Mon, Jun 30, 2008 at 6:12 PM, Rafael Domiciano
<rafael(dot)domiciano(at)gmail(dot)com> wrote:
> No, but is more common Insert and Update than delete.
> While I have around 50.000 Insert and Update, in delete is 5.000
>
> 2008/6/30 Alvaro Herrera <alvherre(at)commandprompt(dot)com>:
>>
>> Rafael Domiciano escribió:
>> > I have schedelus to run vacuum at the night, it starts at 01:00 AM
>>
>> Do you execute lots of updates or deletes on some tables?
>>
>> --
>> Alvaro Herrera
>> http://www.CommandPrompt.com/
>> PostgreSQL Replication, Consulting, Custom Development, 24x7 support
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2008-07-01 01:09:27 | Re: Configuring Shared Buffers |
Previous Message | kevin kempter | 2008-07-01 00:26:24 | Re: pg_tables query issue |