Re: Index space growing even after cleanup via autovacuum in Postgres 9.2 - Mailing list pgsql-general

From Francisco Olarte
Subject Re: Index space growing even after cleanup via autovacuum in Postgres 9.2
Date
Msg-id CA+bJJbx3hfPQFZEWQ-Yzw-vQ2NBCuffW231ATp+cjb+OD6nzyA@mail.gmail.com
Whole thread Raw
In response to Index space growing even after cleanup via autovacuum in Postgres 9.2  (Tirthankar Barari <tbarari@verizon.com>)
Responses Re: Index space growing even after cleanup via autovacuum in Postgres 9.2  (Bill Moran <wmoran@potentialtech.com>)
Re: Index space growing even after cleanup via autovacuum in Postgres 9.2  (Tirthankar Barari <tbarari@verizon.com>)
List pgsql-general
Hi:

On Thu, Jan 9, 2014 at 7:50 PM, Tirthankar Barari <tbarari@verizon.com> wrote:
> We have a table where we insert about 10 million rows everyday. We keep 14
> day's worth of entries (i.e. 140 mil). A scheduled task wakes up every day
> and deletes all entries past the 14 day window (i.e. deletes entries from
> the 15th day in the past).

Not related to your vacuum problem, but if your pattern is something
like deleting everything inserted 15 days ago you may want to think of
using partitioning or simple inheritance. Make the scheduled task
create  a new partition/child table, redirect insertions to it, drop
the oldest partition.

Also, if the pattern is insert-only all the time, delete whole day, it
may be easier to exclude the table from autovacuum and make the
scheduled task vacuum the table after deleting.

Francisco Olarte.


pgsql-general by date:

Previous
From: M Tarkeshwar Rao
Date:
Subject: Re: Consistent file-level backup of pg data directory
Next
From: Amit Langote
Date:
Subject: Re: How to specify/mock the statistic data of tables in PostgreSQL