On Mon, Oct 27, 2014 at 10:38 PM, Rajeev rastogi <rajeev.rast...@huawei.com> wrote: > On 26 October 2014 10:42, Haribabu Kommi wrote: >> I have a question regarding setting of key flags matched. Only the >> first key was set as matched even if we have multiple index conditions. >> Is there any reason behind that? > > Actually the keysCount can be more than one only if the key strategy is > BTEqualStrategyNumber (i.e. = condition) > But our optimization is only for the '>' or '>=' condition only. So adding > code to set flag for all keys is of no use. > > Let me know if I am missing anything here?
Thanks. I understood the point. >> If any volatile function is present in the index condition, the index >> scan itself is not choosen, Is there any need of handling the same >> similar to NULLS? > > Do you mean to say that whether we should add any special handling for > volatile function? > If yes then as you said since index scan itself is not selected for such > functions, then > I feel We don’t need to add anything for that. I also have the same opinion. I marked the patch as ready for committer. Regards, Hari Babu Fujitsu Australia -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
