pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Guillaume Smet <guillaume.smet@gmail.com>
To: Guillaume Smet <guillaume.smet@gmail.com>
To: Florian Weimer <fweimer@bfk.de>
To: pgsql-performance@postgresql.org
Subject: Re: pg_trgm performance
Date: Sat, 24 Feb 2007 02:04:36 +0100
Message-ID: <1d4e0c10702231704y46270252o494b5d6180d7574f@mail.gmail.com> (raw)
In-Reply-To: <20070224003105.GA11010@uio.no>
References: <82mz4k4mt7.fsf@mid.bfk.de>
	<20070115125834.GA28248@uio.no>
	<1d4e0c10702231509k7ad24e2ck3a149a2e3a2899f7@mail.gmail.com>
	<20070224003105.GA11010@uio.no>

Hi Steinar,

On 2/24/07, Steinar H. Gunderson <sgunderson@bigfoot.com> wrote:
> I'm sorry, I can no longer remember where I needed pg_trgm. Simple testing of
> your patch seems to indicate that the GiN version is about 65% _slower_ (18ms
> vs. 30ms) for a test data set I found lying around, but I remember that on
> the data set I needed it, the GIST version was a lot slower than that (think
> 3-400ms). The 18 vs. 30ms test is a random Amarok database, on 8.2.3
> (Debian).

Could you post EXPLAIN ANALYZE for both queries (after 2 or 3 runs)?
And if you can provide  EXPLAIN ANALYZE for a couple of searches
(short length, medium length and long) in both cases, it could be nice
too.

The GiN version is not selective enough currently compared to GiST. It
generally finds the matching rows faster but it has a slower recheck
cond so it's sometimes interesting (in my case) and sometimes not that
interesting (it seems to be your case).

Thanks.

--
Guillaume



view thread (10+ messages)  latest in thread

Message-ID: <1d4e0c10702231704y46270252o494b5d6180d7574f@mail.gmail.com>
Permalink:  ../1d4e0c10702231704y46270252o494b5d6180d7574f@mail.gmail.com/
Also on:    postgresql.org/message-id/1d4e0c10702231704y46270252o494b5d6180d7574f@mail.gmail.com

 · 

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: guillaume.smet@gmail.com, fweimer@bfk.de
  Subject: Re: pg_trgm performance
  In-Reply-To: <1d4e0c10702231704y46270252o494b5d6180d7574f@mail.gmail.com>
  References: <82mz4k4mt7.fsf@mid.bfk.de> <20070115125834.GA28248@uio.no> <1d4e0c10702231509k7ad24e2ck3a149a2e3a2899f7@mail.gmail.com> <20070224003105.GA11010@uio.no> <1d4e0c10702231704y46270252o494b5d6180d7574f@mail.gmail.com>

* 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