From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alex Hunsaker <badalex@gmail.com>
Cc: Zdenek Kotala <Zdenek.Kotala@sun.com>
Cc: Xiao Meng <mx.cogito@gmail.com>
Cc: pgsql-patches@postgresql.org, "Jonah H. Harris" <jonah.harris@gmail.com>
Subject: Re: hash index improving v3
Date: Thu, 04 Sep 2008 21:13:18 -0400
Message-ID: <10995.1220577198@sss.pgh.pa.us> (raw)
In-Reply-To: <34d269d40809041742r6a0703dbgfbdd012f7f19de2e@mail.gmail.com>
References: <ded849dd0808171846g2c6c65adub942bd2510a6c94f@mail.gmail.com>
<48BFDA8D.3080506@sun.com>
<29987.1220560114@sss.pgh.pa.us>
<7627.1220569888@sss.pgh.pa.us>
<34d269d40809041742r6a0703dbgfbdd012f7f19de2e@mail.gmail.com>
"Alex Hunsaker" <badalex@gmail.com> writes:
> Ok let me know if this is to naive of an approach or not hitting the
> right cases you want tested.
You have the unique-versus-not dimension, but I'm also wondering about
narrow vs wide index keys (say about 8 bytes vs 50-100 or so). In the
former case we're not saving any index space by storing only the hash
code, so these could be expected to have different performance
behaviors.
As for specifics of the suggested scripts:
* might be better to do select count(*) not select 1, so that client
communication is minimized
* check that the queries actually use the indexes (not sure that the
proposed switch settings ensure this, not to mention you didn't create
the indexes)
* make sure the pgbench transaction counts are large enough to ensure
significant runtime
* the specific table sizes suggested are surely not large enough
regards, tom lane
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: tgl@sss.pgh.pa.us, badalex@gmail.com, Zdenek.Kotala@sun.com, mx.cogito@gmail.com, jonah.harris@gmail.com
Subject: Re: hash index improving v3
In-Reply-To: <10995.1220577198@sss.pgh.pa.us>
* 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