I read those two links and I dont think that they are relevant because : 1 1)I didnt do any join. 2)I used a where clause in my select
2018-02-04 17:25 GMT+02:00 Justin Pryzby <pry...@telsasoft.com>: > On Sun, Feb 04, 2018 at 05:06:38PM +0200, Mariel Cherkassky wrote: > > 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 ? > > See also: > https://www.postgresql.org/message-id/20170725131650. > GA30519%40telsasoft.com > https://www.postgresql.org/message-id/20170825154434. > GC16287%40telsasoft.com > > Justin > > 2018-02-04 16:54 GMT+02:00 Andreas Kretschmer <andr...@a-kretschmer.de>: > > > > > > > > > Am 04.02.2018 um 13:19 schrieb Mariel Cherkassky: > > > > > >> I checked the plan of the next query : > > >> explain select count(*) from log_full where end_date between > > >> to_date('2017/12/03','YY/MM/DD') and to_date('2017/12/03','YY/MM/ > DD'); > > >> > > >> > > > can you rewrite the query to > > > > > > ... where end_date between '2017/12/03' and '2017/12/03' > > > > > > maybe the planner should be smart enough to do that for you, but > obvously > > > he can't. So it's a workaround, but it seems to solve the problem. >
