Re: postgresql 10.1 wrong plan in when using partitions bug

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Mariel Cherkassky <mariel(dot)cherkassky(at)gmail(dot)com>
Cc: Andreas Kretschmer <andreas(at)a-kretschmer(dot)de>, pgsql-performance(at)lists(dot)postgresql(dot)org
Subject: Re: postgresql 10.1 wrong plan in when using partitions bug
Date: 2018-02-04 15:39:11
Message-ID: 15592.1517758751@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Mariel Cherkassky <mariel(dot)cherkassky(at)gmail(dot)com> writes:
> Great, it solved the issue. Seems problematic that the planner do full
> scans on all partitions in the first case isnt it ? Seems like a bug ?

to_date isn't an immutable function (it depends on timezone and possibly
some other GUC settings). So there's a limited amount that the planner
can do with it.

regards, tom lane

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Mariel Cherkassky 2018-02-04 15:42:23 Re: postgresql 10.1 wrong plan in when using partitions bug
Previous Message Tom Lane 2018-02-04 15:35:32 Re: postgresql 10.1 wrong plan in when using partitions bug