From: Steven Flatt <steven.flatt@gmail.com>
To: Pablo Alcaraz <pabloa@laotraesquina.com.ar>
Cc: pgsql-performance@postgresql.org
Subject: Re: tables with 300+ partitions
Date: Tue, 30 Oct 2007 17:00:10 -0400
Message-ID: <357fa7590710301400x3a05796dle6bae219a1a25fc@mail.gmail.com> (raw)
In-Reply-To: <47277341.7070704@laotraesquina.com.ar>
References: <47277341.7070704@laotraesquina.com.ar>
On 10/30/07, Pablo Alcaraz <pabloa@laotraesquina.com.ar> wrote:
>
> I did some testing. I created a 300 partitioned empty table. Then, I
> inserted some rows on it and the perfomance was SLOW too.
Is the problem with inserting to the partitioned table or selecting from
it? It sounds like inserting is the problem in which case I ask: how are
you redirecting inserts to the appropriate partition? If you're using
rules, then insert performance will quickly degrade with number of
partitions as *every* rule needs to be evaluated for *every* row inserted to
the base table. Using a trigger which you can modify according to some
schedule is much faster, or better yet, use some application-level logic to
insert directly to the desired partition.
Steve
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: steven.flatt@gmail.com, pabloa@laotraesquina.com.ar
Subject: Re: tables with 300+ partitions
In-Reply-To: <357fa7590710301400x3a05796dle6bae219a1a25fc@mail.gmail.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