From: rawi <only4com@web.de>
To: pgsql-sql@postgresql.org
Subject: Re: Index Usage and Running Times by FullTextSearch with prefix matching
Date: Fri, 21 Jun 2013 02:31:29 -0700 (PDT)
Message-ID: <1371807089696-5760297.post@n5.nabble.com> (raw)
In-Reply-To: <22495.1371135398@sss.pgh.pa.us>
References: <1371123556877-5759021.post@n5.nabble.com>
<22495.1371135398@sss.pgh.pa.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-sql>
Tom Lane-2 wrote
> rawi <
> only4com@
> > writes:
>> And querying: FTS with prefix matching:
>
>> SELECT count(a)
>> FROM t1
>> WHERE a_tsvector @@ to_tsquery('aaa:* & b:* & c:* & d:*')
>
>> (RESULT: count: 619)
>> Total query runtime: 21266 ms.
>
> FWIW, I get fairly decent performance for cases like this in HEAD
> (at least with a GIN index; GIST seems much less able to do well with
> short prefixes). What PG version are you testing?
Last tests with PG 9.2:
Whereas the "whole words" full text search stays at ~350ms for 900,000
records I tryed the number of records, which are becoming to make one
suffer, querying for prefixes:
RECORDS RUNTIME (ms)
10,000 13
100,000 81
200,000 172
400,000 7,284
900,000 20,888
Regards, Rawi
--
View this message in context: http://postgresql.1045698.n5.nabble.com/Index-Usage-and-Running-Times-by-FullTextSearch-with-prefix-...
Sent from the PostgreSQL - sql mailing list archive at Nabble.com.
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
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-sql@postgresql.org
Cc: only4com@web.de
Subject: Re: Index Usage and Running Times by FullTextSearch with prefix matching
In-Reply-To: <1371807089696-5760297.post@n5.nabble.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