| From: | Mariel Cherkassky <mariel(dot)cherkassky(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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:42:23 |
| Message-ID: | CA+t6e1=yXX0JvMTCs6+fjQiZ8VDf5bTgYqBxtwx_bLWW+S+YtQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Hi Tom,
Did you hear about any solution that is similar to oracle`s global index ?
Is there any way to query all the partitions with one index?
2018-02-04 17:39 GMT+02:00 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> 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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rick Otten | 2018-02-04 16:04:56 | Re: postgresql 10.1 wrong plan in when using partitions bug |
| Previous Message | Tom Lane | 2018-02-04 15:39:11 | Re: postgresql 10.1 wrong plan in when using partitions bug |