From: Ben <midfield@gmail.com>
To: Igor Neyman <ineyman@perceptron.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: partitioning question 1
Date: Fri, 29 Oct 2010 09:16:13 -0700
Message-ID: <59555E0F-71C2-4062-AD23-F1B7B9993354@gmail.com> (raw)
In-Reply-To: <F4C27E77F7A33E4CA98C19A9DC6722A206ADF39A@EXCHANGE.corp.perceptron.com>
References: <A9A748D8-A52F-4C16-A303-3A4AA1EC1BD2@gmail.com>
<F4C27E77F7A33E4CA98C19A9DC6722A206ADF39A@EXCHANGE.corp.perceptron.com>
On Oct 29, 2010, at 7:38 AM, Igor Neyman wrote:
>> is my intuition completely off on this?
>>
>> best regards, ben
>>
>
> If your SELECT retrieves substantial amount of records, table scan could
> be more efficient than index access.
>
> Now, if while retrieving large amount of records "WHERE clause" of this
> SELECT still satisfies constraints on some partition(s), then obviously
> one (or few) partition scans will be more efficient than full table scan
> of non-partitioned table.
>
> So, yes partitioning provides performance improvements, not only
> maintenance convenience.
my impression was that a *clustered* index would give a lot of the same I/O benefits, in a more flexible way. if you're clustered on the column in question, then an index scan for a range is much like a sequential scan over a partition (as far as i understand.)
b
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: midfield@gmail.com, ineyman@perceptron.com
Subject: Re: partitioning question 1
In-Reply-To: <59555E0F-71C2-4062-AD23-F1B7B9993354@gmail.com>
References: <A9A748D8-A52F-4C16-A303-3A4AA1EC1BD2@gmail.com> <F4C27E77F7A33E4CA98C19A9DC6722A206ADF39A@EXCHANGE.corp.perceptron.com> <59555E0F-71C2-4062-AD23-F1B7B9993354@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