From: Steinar H. Gunderson <sgunderson@bigfoot.com>
To: pgsql-performance@postgresql.org
Subject: Re: Seqscan rather than Index
Date: Sat, 18 Dec 2004 14:45:40 +0100
Message-ID: <20041218134540.GA25107@uio.no> (raw)
In-Reply-To: <20041218043918.GA20619@wolff.to>
References: <20041217011853.9E8FF3CADB0@svr1.postgresql.org>
<41C2D936.3060901@archonet.com>
<87acsdkjte.fsf@stark.xeocode.com>
<20041217215627.GC8281@uio.no>
<20041218043918.GA20619@wolff.to>
On Fri, Dec 17, 2004 at 10:39:18PM -0600, Bruno Wolff III wrote:
> It doesn't seem totally out of wack. You will be limited by the memory
> bandwidth and it looks like you get something on the order of a few
> hundred references to memory per row. That may be a little high, but
> it doesn't seem ridiculously high.
I just tested 8.0.0rc1 -- I got a _50%_ speedup on this operation...
/* Steinar */
--
Homepage: http://www.sesse.net/
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: sgunderson@bigfoot.com
Subject: Re: Seqscan rather than Index
In-Reply-To: <20041218134540.GA25107@uio.no>
* 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