+91-9953975849 <+91%2099539%2075849> | Ext 1078
>> |dinesh.chan...@cyient.com
>>
>> Plot No. 7, NSEZ, Phase-II ,Noida-Dadri Road, Noida - 201 305,India.
>>
>>
>>
>> *From:* Madusudanan.B.N [mailto:b.n.madusuda...@gmail.com]
>> *Sent:* 20 January, 2017 5:
ease contact the sender by reply email and destroy
> all copies of the original message. Check all attachments for viruses
> before opening them. All views or opinions presented in this e-mail are
> those of the author and may not reflect the opinion of Cyient or those of
> our affiliates.
>
--
Regards,
Madusudanan.B.N <http://madusudanan.com>
rly selective (having now() as the
> default over a long period of time), this surprises me.
>
> With a normal btree index, of course, it runs fine:
>
> https://explain.depesz.com/s/TB5
>
>
> Any ideas?
>
>
--
Regards,
Madusudanan.B.N <http://madusudanan.com>
le"."id" =
> "table_b"."big_table_id")
> WHERE
> "table_b"."item_id" IN ();
>
>
> As you can imagine we would be very glad to solve this issue with a single
> query and without having to re-code existing logic of PostgreSQL. But how?
>
>
> Best,
> Sven
>
>
> PS: if you require EXPLAIN ANALYZE, I can post them as well.
>
>
> --
> Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-performance
>
--
Regards,
Madusudanan.B.N <http://madusudanan.com>
