Re: [PERFORM] Query planner chooses index scan backward instead of better index option

2016-11-17 Thread Seckin Pulatkan
After Jeff Janes' reply, I have tried a couple of limit values and found at the current state of data, 90 was a change on the query planner. explain (analyze, buffers) select booking0_.* from booking booking0_ where (booking0_.customer_id in (select customer1_.id from customer cust

Re: [PERFORM] Query planner chooses index scan backward instead of better index option

2016-11-15 Thread Seckin Pulatkan
red hit=12 read=4 Planning time: 39.774 ms Execution time: 92.085 ms Regards, Seckin ps: sorry Jeff for double email. On Mon, Nov 14, 2016 at 7:50 PM, Jeff Janes wrote: > On Mon, Nov 14, 2016 at 4:01 AM, Seckin Pulatkan > wrote: > >> Hi, >> >> On our producti

[PERFORM] Query planner chooses index scan backward instead of better index option

2016-11-14 Thread Seckin Pulatkan
Hi, On our production environment (PostgreSQL 9.4.5 on x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-4), 64-bit), one of our queries runs very slow, about 5 minutes . We noticed that it does not use an index that we anticapited it would. The query is select bookin