Re: postgresql 10.1 wrong plan in when using partitions bug - Mailing list pgsql-performance

From Rick Otten
Subject Re: postgresql 10.1 wrong plan in when using partitions bug
Date
Msg-id CAMAYy4+aRYSRE0--nE-5eJ5XRTsdO8R491FLwF3uYjbvba2AQg@mail.gmail.com
Whole thread Raw
In response to Re: postgresql 10.1 wrong plan in when using partitions bug  (legrand legrand <legrand_legrand@hotmail.com>)
List pgsql-performance


On Sun, Feb 4, 2018 at 8:19 AM, legrand legrand <legrand_legrand@hotmail.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.


pgsql-performance by date:

Previous
From: legrand legrand
Date:
Subject: Re: postgresql 10.1 wrong plan in when using partitions bug
Next
From: Mariel Cherkassky
Date:
Subject: Re: postgresql 10.1 wrong plan in when using partitions bug