Re: [PERFORM] less than 2 sec for response - possible?

Hello Have you solved your problem ? Could it be a conversion overhead from 'timestamp without time zone' to 'date' ? In this case, I don't know if planer store constants as date or timestamp. Mathieu Pujol Le 02/07/2016 à 04:48, trafdev a écrit : Thanks Tom. I've created index on aid, da

Re: [PERFORM] GIST optimization to limit calls to operator on sub nodes

Le 30/06/2014 16:04, Tom Lane a écrit : Pujol Mathieu writes: Le 29/06/2014 22:30, Tom Lane a écrit : I don't actually understand what's being requested here that the NotConsistent case doesn't already cover. The NotConsistent case is correctly covered, the sub nodes are not

Re: [PERFORM] GIST optimization to limit calls to operator on sub nodes

Le 29/06/2014 22:30, Tom Lane a écrit : Emre Hasegeli writes: Pujol Mathieu : I made my own index to handle specific data and operators. It works pretty fine but I wonder if it was possible to optimize it. When I run my operator on a GIST node (in the method gist_range_consistent) it returns

Re: [PERFORM] GIST optimization to limit calls to operator on sub nodes

Le 29/06/2014 22:14, Emre Hasegeli a écrit : Pujol Mathieu : Hello, I already post my question in the General Mailing list, but without succeed so I try this one that seems to me more specialized. My question is about GIST index. I made my own index to handle specific data and operators. It

[PERFORM] GIST optimization to limit calls to operator on sub nodes

Hello, I already post my question in the General Mailing list, but without succeed so I try this one that seems to me more specialized. My question is about GIST index. I made my own index to handle specific data and operators. It works pretty fine but I wonder if it was possible to optimize it