From: Tom Lane <tgl@sss.pgh.pa.us>
To: Job <Job@colliniconsulting.it>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Strong slowdown on huge tables
Date: Tue, 29 May 2012 13:42:42 -0400
Message-ID: <14867.1338313362@sss.pgh.pa.us> (raw)
In-Reply-To: <88EF58F000EC4B4684700C2AA3A73D7AA8B1042B83@W2008DC01.ColliniConsulting.lan>
References: <88EF58F000EC4B4684700C2AA3A73D7AA8B1042B83@W2008DC01.ColliniConsulting.lan>
Job <Job@colliniconsulting.it> writes:
> i use PostgreSQL 8.4.8 on Centos 5.x and i have some table where i load with pg_bulkload webtraffic logs, every day.
> After loading new data, i delete with a query 30-days older logs.
Since the deletion pattern is so predictable, you should consider
setting this table up as a partitioned table, so that you can just drop
the oldest partition instead of having to rely on DELETE+VACUUM to
reclaim space. See
http://www.postgresql.org/docs/8.4/static/ddl-partitioning.html
Alternatively, look into whether including a manual VACUUM in your daily
update script helps any.
regards, tom lane
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-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, Job@colliniconsulting.it
Subject: Re: Strong slowdown on huge tables
In-Reply-To: <14867.1338313362@sss.pgh.pa.us>
* 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