Re: Optimizer improvements: to do or not to do?

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Cc: "Say42" <andrews42(at)yandex(dot)ru>
Subject: Re: Optimizer improvements: to do or not to do?
Date: 2006-09-12 14:16:50
Message-ID: 200609121616.51674.peter_e@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Naz Gassiep 2006-09-12 14:31:59 Re: dump / restore functionality
Previous Message Tom Lane 2006-09-12 14:16:46 Re: Optimizer improvements: to do or not to do?