Re: sequential scan on child partition tables

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Anj Adu <fotographs(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-performance(at)postgresql(dot)org
Subject: Re: sequential scan on child partition tables
Date: 2009-10-18 05:08:46
Message-ID: dcc563d10910172208g21b751b3p626c5a55b75f960a@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Thu, Oct 15, 2009 at 2:51 PM, Anj Adu <fotographs(at)gmail(dot)com> wrote:
> This appears to be a bug in the optimizer with resepct to planning
> queries involving child partitions. It is clear that "any" index is
> being ignored even if the selectivity is high. I had to re-write the
> same query by explicitly "union-all" ' ing  the queries for individual
> partitions.

So, did adjusting cost parameters help at all?

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Euler Taveira de Oliveira 2009-10-18 05:33:27 Re: Issues with \copy from file
Previous Message Melton Low 2009-10-18 05:07:36 Re: table full scan or index full scan?