Re: Paritioning vs. caching

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Konrad Garus <konrad(dot)garus(at)gmail(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Paritioning vs. caching
Date: 2010-03-08 20:30:03
Message-ID: 4B955E4B.9060805@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance


> 1. When I query the table by ID, it performs index scan on each
> partition. The result is only found in one partition, but I understand
> why it needs to look in all of them. How much disk reading does it
> involve? Is only the "head" of indexes for partitions that do not
> include the row scanned, or are always whole indexes read? I would
> like to know the general rule for index scans.

If you're not including the partition criterion in most of your queries,
you're probably partitioning on the wrong value.

--Josh Berkus

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Greg Smith 2010-03-08 20:50:36 Re: Testing FusionIO
Previous Message Anj Adu 2010-03-08 19:27:00 Re: Paritioning vs. caching