pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Matthew Wakeling <matthew@flymine.org>
To: pgsql-performance@postgresql.org
Subject: Re: Tsearch2 Initial Search Speed
Date: Tue, 17 Jun 2008 12:00:24 +0100 (BST)
Message-ID: <Pine.LNX.4.64.0806171154380.3987@aragorn.flymine.org> (raw)
In-Reply-To: <485789C1.3000803@selestial.com>
References: <4856A91F.1020001@selestial.com>
	<200806161124.57543@hal.medialogik.com>
	<485789C1.3000803@selestial.com>

On Tue, 17 Jun 2008, Howard Cole wrote:
> Alan Hodgson wrote:
>> It's because everything is cached, in particular the relevant rows from the 
>> "email" table (accessing which took 22 of the original 27 seconds).

> Thanks Alan, I guessed that the caching was the difference, but I do not 
> understand why there is a heap scan on the email table? The query seems to 
> use the email_fts_index correctly, which only takes 6 seconds, why does it 
> then need to scan the email table?

It's not a sequential scan - that really would take a fair time. It's a 
bitmap heap scan - that is, it has built a bitmap of the rows needed by 
using the index, and now it needs to fetch all those rows from the email 
table. There's 14938 of them, and they're likely scattered all over the 
table, so you'll probably have to do 14938 seeks on the disc. At 5ms a 
pop, that would be 70 seconds, so count yourself lucky it only takes 22 
seconds instead!

If you aren't actually interested in having all 14938 rows splurged at 
you, try using the LIMIT keyword at the end of the query. That would make 
it run a bit faster, and would make sense if you only want to display the 
first twenty on a web page or something.

Matthew

-- 
For every complex problem, there is a solution that is simple, neat, and wrong.
                                                      -- H. L. Mencken 



view thread (18+ messages)  latest in thread

Message-ID: <Pine.LNX.4.64.0806171154380.3987@aragorn.flymine.org>
Permalink:  ../Pine.LNX.4.64.0806171154380.3987@aragorn.flymine.org/
Also on:    postgresql.org/message-id/Pine.LNX.4.64.0806171154380.3987@aragorn.flymine.org

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: matthew@flymine.org
  Subject: Re: Tsearch2 Initial Search Speed
  In-Reply-To: <Pine.LNX.4.64.0806171154380.3987@aragorn.flymine.org>
  References: <4856A91F.1020001@selestial.com> <200806161124.57543@hal.medialogik.com> <485789C1.3000803@selestial.com> <Pine.LNX.4.64.0806171154380.3987@aragorn.flymine.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