From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Manfred Koizar <mkoi-pg(at)aon(dot)at> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: effective_cache_size |
Date: | 2002-07-11 14:11:25 |
Message-ID: | 16709.1026396685@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Manfred Koizar <mkoi-pg(at)aon(dot)at> writes:
> The estimator only uses effective_cache_size, it never looks at
> NBuffers. So shouldn't we add
> if (effective_cache_size < NBuffers)
Pretty useless considering that effective_cache_size can be SET on the
fly...
In general, my philosophy has been not to constrain settings of
optimizer cost parameters more than absolutely necessary. For example,
the system will let you set random_page_cost to values between 0 and 1,
even though values less than 1 are surely nonsensical. Once in a while
someone might want to do that just for testing purposes...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2002-07-11 14:47:09 | Re: Proposal: CREATE CONVERSION |
Previous Message | Tom Lane | 2002-07-11 14:06:36 | Re: workaround for lack of REPLACE() function |