From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | "Dan Kaplan" <dkaplan(at)citizenhawk(dot)com> |
Cc: | <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: t1.col like '%t2.col%' |
Date: | 2008-02-29 23:56:42 |
Message-ID: | 20080229155642.20ac07be@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, 29 Feb 2008 15:52:31 -0800
"Dan Kaplan" <dkaplan(at)citizenhawk(dot)com> wrote:
> I learned a little about pg_trgm here:
> http://www.sai.msu.su/~megera/postgres/gist/pg_trgm/README.pg_trgm
>
> But this seems like it's for finding similarities, not substrings.
> How can I use it to speed up t1.col like '%t2.col%'?
Faster disks.
No matter what, that will seqscan. So if you want it to go faster, you
need faster hardware.
Sincerely,
Joshua D. Drake
- --
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Community Conference: http://www.postgresqlconference.org/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL SPI Liaison | SPI Director | PostgreSQL political pundit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHyJu9ATb/zqfZUUQRAlPwAJ9XZvoWvNquuWGytvJfNlm79LBvtwCbBwRw
uqb7fhD5+w87BzUoVEjICEY=
=z5xQ
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory Williamson | 2008-03-01 00:30:08 | Re: t1.col like '%t2.col%' |
Previous Message | Dan Kaplan | 2008-02-29 23:52:31 | Re: t1.col like '%t2.col%' |