From: Tom Lane <tgl@sss.pgh.pa.us>
To: 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: Sun, 20 Mar 2005 18:01:49 -0500
Message-ID: <14172.1111359709@sss.pgh.pa.us> (raw)
In-Reply-To: <002a01c52d87$543d1010$0200a8c0@grownups>
References: <200503191202.38089.josh@agliodbs.com>
<op.snwojdwith1vuj@localhost>
<20050319225624.GA8467@dcc.uchile.cl>
<3404.1111277153@sss.pgh.pa.us>
<002a01c52d87$543d1010$0200a8c0@grownups>
"Stacy White" <harsh@computer.org> writes:
> FWIW, we see large benefits from partitioning other than the ability to
> easily drop data, for example:
> - We can vacuum only the active portions of a table
> - Postgres automatically keeps related records clustered together on disk,
> which makes it more likely that the blocks used by common queries can be
> found in cache
> - The query engine uses full table scans on the relevant sections of data,
> and quickly skips over the irrelevant sections
> - 'CLUSTER'ing a single partition is likely to be significantly more
> performant than clustering a large table
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 ...
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, 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: <14172.1111359709@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