Re: postgresql 10.1 wrong plan in when using partitions bug

From: Rick Otten <rottenwindfish(at)gmail(dot)com>
To: legrand legrand <legrand_legrand(at)hotmail(dot)com>
Cc: "pgsql-performa(dot)" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: postgresql 10.1 wrong plan in when using partitions bug
Date: 2018-02-04 13:38:46
Message-ID: CAMAYy4+aRYSRE0--nE-5eJ5XRTsdO8R491FLwF3uYjbvba2AQg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Sun, Feb 4, 2018 at 8:19 AM, legrand legrand <legrand_legrand(at)hotmail(dot)com
> wrote:

> What is the value of guc constrain_exclusion ?
>
>
>
In my use case, which is a big union all behind a view, setting this to
off, on, or partition makes no difference. It still sequence scans all of
the sub-tables in pg 10.1 whereas it used the indexes in 9.6.

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Mariel Cherkassky 2018-02-04 13:43:08 Re: postgresql 10.1 wrong plan in when using partitions bug
Previous Message legrand legrand 2018-02-04 13:29:02 Re: postgresql 10.1 wrong plan in when using partitions bug