From: Joshua D. Drake <jd@commandprompt.com>
To: Dan Kaplan <dkaplan@citizenhawk.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: t1.col like '%t2.col%'
Date: Fri, 29 Feb 2008 15:56:42 -0800
Message-ID: <20080229155642.20ac07be@commandprompt.com> (raw)
In-Reply-To: <001401c87b2e$26386000$1d00a8c0@dan>
References: <00c001c87975$a907e2e0$1d00a8c0@dan>
<Pine.LNX.4.64.0802280833040.31180@sn.sai.msu.ru>
<001401c87b2e$26386000$1d00a8c0@dan>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, 29 Feb 2008 15:52:31 -0800
"Dan Kaplan" <dkaplan@citizenhawk.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-----
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-performance@postgresql.org
Cc: jd@commandprompt.com, dkaplan@citizenhawk.com
Subject: Re: t1.col like '%t2.col%'
In-Reply-To: <20080229155642.20ac07be@commandprompt.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