Re: sequential scan on child partition tables

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The actual data returned is a tiny fraction of the total table volume.

Is there a way to force an index scan on the partitions in a
guaranteed manner without resorting to re-writing queries with the
union all on partitions.

Thank you

Sriram

On Wed, Oct 14, 2009 at 10:15 PM, Tom Lane <tgl@xxxxxxxxxxxxx> wrote:
> Anj Adu <fotographs@xxxxxxxxx> writes:
>> This query is doing a sequential scan on the child partitions even
>> though indexes on all constrained columns are present
>
> It looks to me like it's doing exactly what it is supposed to, ie,
> indexscan on the partitions where it would help and seqscans on the
> partitions where it wouldn't.  Indexscan is not better than seqscan
> for retrieving all or most of a table.
>
>                        regards, tom lane
>

-- 
Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance


[Postgresql General]     [Postgresql PHP]     [PHP Users]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Yosemite]

  Powered by Linux