Re: Paritioning vs. caching - Mailing list pgsql-performance

From Josh Berkus
Subject Re: Paritioning vs. caching
Date
Msg-id 4B955E4B.9060805@agliodbs.com
Whole thread Raw
In response to Paritioning vs. caching  (Konrad Garus <konrad.garus@gmail.com>)
List 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

pgsql-performance by date:

Previous
From: Anj Adu
Date:
Subject: Re: Paritioning vs. caching
Next
From: Greg Smith
Date:
Subject: Re: Testing FusionIO