> On Oct 26, 2017, at 1:02 AM, Laurenz Albe <laurenz.albe@cybertec.at> wrote:
>
> Rob Sargent wrote:
>> I have a query I cannot tame and I'm wondering if there's an alternative
>> to the "between" clause I'm using. Perhaps a custom type could do
>> better? I've tried the "<@" orperator and that changes the query plan
>> significantly but the execution cost/time is not improved.
>>
>> Any suggestion or pointers much appreciated.
>
> You really need EXPLAIN (ANALYZE, BUFFERS) output to be able to
> undersrand what is going on.
>
> A couple of simple things to check:
>
> - Have all tables been ANALYZED beforehand?
> - Are all optimizer database parameters identical?
>
> Also, to have PostgreSQL inline the function, which would be good
> for performance, it should be declared IMMUTABLE.
>
> Yours,
> Laurenz Albe
The explain analyze was (maybe is)still running but without buffers.
Thought of the immutable bit. Will be doing that test.
All tables vacuumed and analyzed with each structural change.
Thanks
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general