From: Abhijit Menon-Sen <ams@oryx.com>
To: Gregory Stark <stark@enterprisedb.com>
Cc: Zoltan Boszormenyi <zb@cybertec.at>
Cc: pgsql-hackers@postgresql.org
Subject: Re: posix advises ...
Date: Sat, 12 Jul 2008 17:04:32 +0530
Message-ID: <20080712113432.GA26415@toroid.org> (raw)
In-Reply-To: <87abgo0yid.fsf@oxford.xeocode.com>
References: <4826C200.8060807@cybertec.at>
<Pine.GSO.4.64.0805132139250.20823@westnet.com>
<485A3F20.1080907@cybertec.at>
<20080711100215.GA14893@toroid.org>
<87abgo0yid.fsf@oxford.xeocode.com>
At 2008-07-12 00:52:42 +0100, stark@enterprisedb.com wrote:
>
> There was some discussion about this change and in fact if you
> look at CVS HEAD you'll find it already applied.
Not as far as I can see.
> Incrementing the most significant index keys would maximize the
> distance we're jumpin around in the index tree.
I see. Thanks.
> The later versions of mine had a GUC named effective_spindle_count
> which I think is nicely abstracted away from the implementation
> details.
Yes, that does sound much better. (The patch I read had a
preread_pages_bitmapscan variable instead.)
-- ams
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-patches@postgresql.org
Cc: ams@oryx.com, stark@enterprisedb.com, zb@cybertec.at, pgsql-hackers@postgresql.org
Subject: Re: posix advises ...
In-Reply-To: <20080712113432.GA26415@toroid.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