We have contrib/wildspeed extension which uses new partial
match feature of GIN index. See our presentation
http://www.pgcon.org/2008/schedule/events/58.en.html
It index all permutations, so index is very big, but for not
long read-only sstring it works fast.
Oleg
On Tue, 22 Jul 2008, Stefan St
"Dann Corbit" <[EMAIL PROTECTED]> writes:
>>> I'm developing a autocomplete Feature using php and PostgreSQL 8.3.
>>> To fill the autocomplete box I use the following SQL Statement:
>>> select * from _table_ where upper( _field_ ) like '%STRING%';
>>> This SQL Statement takes 900 ms on a Table with
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dann Corbit
Sent: Tuesday, July 22, 2008 1:30 PM
To: Stefan Sturm; pgsql-general@postgresql.org
Subject: Re: [GENERAL] Optimizing a like-cause
-Original Message-
From: [EMAIL PROTECTED]
[mailto
>
> Hello,
>
> I'm developing a autocomplete Feature using php and PostgreSQL 8.3.
> To fill the autocomplete box I use the following SQL Statement:
> select * from _table_ where upper( _field_ ) like '%STRING%';
>
> This SQL Statement takes 900 ms on a Table with 300.000 entries.
>
> What can
On Tuesday 22 July 2008, Stefan Sturm <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I'm developing a autocomplete Feature using php and PostgreSQL 8.3.
> To fill the autocomplete box I use the following SQL Statement:
> select * from _table_ where upper( _field_ ) like '%STRING%';
>
> This SQL Statement
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Stefan Sturm
Sent: Tuesday, July 22, 2008 11:31 AM
To: pgsql-general@postgresql.org
Subject: [GENERAL] Optimizing a like-cause
Hello,
I'm developing a autocomplete Feature using php and PostgreSQL 8.
Hello,
I'm developing a autocomplete Feature using php and PostgreSQL 8.3.
To fill the autocomplete box I use the following SQL Statement:
select * from _table_ where upper( _field_ ) like '%STRING%';
This SQL Statement takes 900 ms on a Table with 300.000 entries.
What can I do to speed up the
