From: Yann Michel <yann-postgresql@spline.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Stacy White <harsh@computer.org>
Cc: Alvaro Herrera <alvherre@dcc.uchile.cl>
Cc: PFC <lists@boutiquenumerique.com>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: What needs to be done for real Partitioning?
Date: Wed, 27 Apr 2005 15:31:39 +0200
Message-ID: <20050427133139.GA3700@zoom.spline.inf.fu-berlin.de> (raw)
In-Reply-To: <14172.1111359709@sss.pgh.pa.us>
References: <200503191202.38089.josh@agliodbs.com>
<op.snwojdwith1vuj@localhost>
<20050319225624.GA8467@dcc.uchile.cl>
<3404.1111277153@sss.pgh.pa.us>
<002a01c52d87$543d1010$0200a8c0@grownups>
<14172.1111359709@sss.pgh.pa.us>
Hi,
On Sun, Mar 20, 2005 at 06:01:49PM -0500, Tom Lane wrote:
> Global indexes would seriously reduce the performance of both vacuum and
> cluster for a single partition, and if you want seq scans you don't need
> an index for that at all. So the above doesn't strike me as a strong
> argument for global indexes ...
I'd like to describe a usecase where a global index is usefull.
We have a datawarehouse with invoices for a rolling window of a few
years. Each invoice has several positions so a uk is
(invoice,position). Dur to the fact that most of the queries are only on
a few months or some quarters of a year, our pk starts with the
time-attribute (followed by the dimension ids) which is the partition
key (range). During the nightly update, we receive each updated invoice
so we have to update that special (global unique) row which is resolved
very fast by using the uk.
So you can see, that there is a usefull case for providing a global
index while using partitining and local indexes as well.
Regards,
Yann
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: yann-postgresql@spline.de, tgl@sss.pgh.pa.us, harsh@computer.org, alvherre@dcc.uchile.cl, lists@boutiquenumerique.com, josh@agliodbs.com
Subject: Re: What needs to be done for real Partitioning?
In-Reply-To: <20050427133139.GA3700@zoom.spline.inf.fu-berlin.de>
References: <200503191202.38089.josh@agliodbs.com> <op.snwojdwith1vuj@localhost> <20050319225624.GA8467@dcc.uchile.cl> <3404.1111277153@sss.pgh.pa.us> <002a01c52d87$543d1010$0200a8c0@grownups> <14172.1111359709@sss.pgh.pa.us> <20050427133139.GA3700@zoom.spline.inf.fu-berlin.de>
* 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