From: Steven Flatt <steven.flatt@gmail.com>
To: Simon Riggs <simon@2ndquadrant.com>
Cc: Colin Taylor <colin.taylor@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: table partioning performance
Date: Wed, 10 Jan 2007 16:00:00 -0500
Message-ID: <357fa7590701101300m2812545k1487ca58e97970ed@mail.gmail.com> (raw)
In-Reply-To: <1168346933.3951.276.camel@silverbirch.site>
References: <84d3067d0701062037k3229c9ddjbde73b1fd79ee209@mail.gmail.com>
<357fa7590701081202p726c049ej61390dd1816d1369@mail.gmail.com>
<1168346933.3951.276.camel@silverbirch.site>
On 1/9/07, Simon Riggs <simon@2ndquadrant.com> wrote:
>
> If you are doing date range partitioning it should be fairly simple to
> load data into the latest table directly. That was the way I originally
> intended for it to be used. The rules approach isn't something I'd
> recommend as a bulk loading option and its a lot more complex anyway.
>
The problem we have with blindly loading all data into the latest table is
that some data (< 5%, possibly even much less) is actually delivered "late"
and belongs in earlier partitions. So we still needed the ability to send
data to an arbitrary 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, simon@2ndquadrant.com, colin.taylor@gmail.com
Subject: Re: table partioning performance
In-Reply-To: <357fa7590701101300m2812545k1487ca58e97970ed@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