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

Re: Configuring Shared Buffers

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: (view raw, whole thread or download thread mbox)
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

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
>> PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

pgsql-admin by date

Next:From: Alvaro HerreraDate: 2008-07-01 01:09:27
Subject: Re: Configuring Shared Buffers
Previous:From: kevin kempterDate: 2008-07-01 00:26:24
Subject: Re: pg_tables query issue

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