Re: Index Scan cost expression

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Amit Gupta <amit(dot)pc(dot)gupta(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Index Scan cost expression
Date: 2009-01-27 14:54:00
Message-ID: 14203.1233068040@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Amit Gupta <amit(dot)pc(dot)gupta(at)gmail(dot)com> writes:
> Upon taking a cursory look at the cost functions of other operators, I
> realized that available memory (effective_cache_size) is not
> considered for estimating the costs of hash/sort/NLjoin/etc. Why is
> that the case?

The relevant number for those is work_mem not effective_cache_size.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2009-01-27 14:54:02 Re: pg_upgrade project status
Previous Message Tom Lane 2009-01-27 14:52:15 Re: pg_upgrade project status