Re: Optimizer improvements: to do or not to do? - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Optimizer improvements: to do or not to do?
Date
Msg-id 200609121616.51674.peter_e@gmx.net
Whole thread Raw
In response to Re: Optimizer improvements: to do or not to do?  ("Say42" <andrews42@yandex.ru>)
List pgsql-hackers
Am Dienstag, 12. September 2006 12:48 schrieb Say42:
> That is why caching should be taking into account
> during joining cost calculation.

If you know of a more effective way to do that beyond the effective_cache_size 
parameter that we have now, let us know.

-- 
Peter Eisentraut
http://developer.postgresql.org/~petere/


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: dump / restore functionality
Next
From: Tom Lane
Date:
Subject: Re: Optimizer improvements: to do or not to do?