-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 29 Feb 2008 15:52:31 -0800 "Dan Kaplan" <dkaplan@xxxxxxxxxxxxxxx> 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----- ---------------------------(end of broadcast)---------------------------TIP 5: don't forget to increase your free space map settings
