From: William Yu <wyu@talisys.com>
To: pgsql-performance@postgresql.org
Subject: Re: why do optimizer parameters have to be set manually?
Date: Fri, 19 Dec 2003 09:44:17 -0800
Message-ID: <brvddd$1u7p$1@news.hub.org> (raw)
In-Reply-To: <9382.1071846435@sss.pgh.pa.us>
References: <3FE1F5A1.6080908@geizhals.at>
<22686.1071777380@sss.pgh.pa.us>
<3FE302D2.7080901@geizhals.at>
<9382.1071846435@sss.pgh.pa.us>
Tom Lane wrote:
> easy or cheap to get a measurement that isn't skewed by kernel caching
> behavior. (You need a test file significantly larger than RAM, and
> even then you'd better repeat the measurement quite a few times to see
> how much noise there is in it.)
I found a really fast way in Linux to flush the kernel cache and that is
to unmount the drive and then remount. Beats having to read though a
file > RAM everytime.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: wyu@talisys.com
Subject: Re: why do optimizer parameters have to be set manually?
In-Reply-To: <brvddd$1u7p$1@news.hub.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox