From: Monika Cernikova <monika@microstep-mis.com>
To: pgsql-general@postgresql.org
To: pgsql-admin@postgresql.org
Subject: index bloat problem
Date: Fri, 09 Mar 2007 11:05:14 +0100
Message-ID: <45F1315A.1020906@microstep-mis.com> (raw)
I use Postgres 8.1 on linux
I have several tables to which I need insert about 200-500 records per
minute.
Records contains timestamp (actual time), and this timestamp is part of
primary key and index.
I need to keep data for 1 month. I daily delete data older than 1 month
and than run vacuum analyze.
Size of primary keys and indexes still grows.
(After 2 months database size is about 35G and vacuum runs about 20 hours.
When I dumped and restored database, new size was 25G. Indexes and
constraints had half size)
Can you help me how to stop index growing or reindex database if I CAN'T
STOP writing records?
Thanx,
Monika
Here are my settings in postgresql.conf, that differs from defaults
shared_buffers = 2000
max_fsm_pages = 400000
(it isn't much, but there isn't logged in vacuum log that it needs more)
vacuum_cost_delay = 100
vacuum_cost_page_hit = 6
vacuum_cost_limit = 100
wal_buffers = 16
checkpoint_segments = 8
autovacuum = off
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: monika@microstep-mis.com, pgsql-general@postgresql.org
Subject: Re: index bloat problem
In-Reply-To: <45F1315A.1020906@microstep-mis.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox