From: Craig Ringer <craig@postnewspapers.com.au>
To: Nickolay <nitro@zhukcity.ru>
Cc: pgsql-performance@postgresql.org
Subject: Re: PG optimization question
Date: Sun, 10 Jan 2010 09:24:26 +0800
Message-ID: <4B492C4A.2000403@postnewspapers.com.au> (raw)
In-Reply-To: <4B485B47.1000205@zhukcity.ru>
References: <4B485B47.1000205@zhukcity.ru>
On 9/01/2010 6:32 PM, Nickolay wrote:
> Hi 2 all,
>
> Here is my typical configuration: 1(2) GB of RAM, HP ML 350(150) series
> server, SATA raid, Linux.
>
> I have 1 big table (called "archive") which contains short text messages
> with a plenty of additional service info.
> Currently this table contains more than 4M rows for a period of 4,5
> months, i.e. each row has average size of 1K.
>
> I'm going to make our application work with partitions of this table
> instead of one large table. The primary reason is that eventually we'd
> need to remove old rows and it would be pretty hard with one table
> because of blocking (and rows are being added constantly).
DELETEs shouldn't block concurrent INSERTs.
That said, dropping a partition is a lot more convenient than DELETEing
from a big table.
--
Craig Ringer
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: craig@postnewspapers.com.au, nitro@zhukcity.ru
Subject: Re: PG optimization question
In-Reply-To: <4B492C4A.2000403@postnewspapers.com.au>
* 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