Skip site navigation (1) Skip section navigation (2)

Re: EFFECTIVE_CACHE_SIZE

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Joseph Shraibman <jks(at)selectacast(dot)net>
Cc: postgres <pgsql-general(at)postgresql(dot)org>
Subject: Re: EFFECTIVE_CACHE_SIZE
Date: 2003-06-18 00:13:24
Message-ID: 17970.1055895204@sss.pgh.pa.us (view raw, whole thread or download thread mbox)
Thread:
Lists: pgsql-general
Joseph Shraibman <jks(at)selectacast(dot)net> writes:
> What is the effect of EFFECTIVE_CACHE_SIZE?  What happens if I set it too low or too high?
> Does a higher setting bias the planner more toward seq scans?

No, it'd bias towards indexscans.  IIRC the parameter is only used to
cost indexscans, and a larger value will tend to make indexscans look
cheaper.

			regards, tom lane

In response to

pgsql-general by date

Next:From: Martijn van OosterhoutDate: 2003-06-18 00:18:53
Subject: Re: Sort memory not being released
Previous:From: Tom LaneDate: 2003-06-18 00:12:18
Subject: Re: [PERFORM] Interesting incosistent query timing

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group