summaryrefslogtreecommitdiff
path: root/contrib/pg_trgm/pg_trgm.sql.in
Commit message (Collapse)AuthorAgeFilesLines
* Convert contrib modules to use the extension facility.Tom Lane2011-02-131-155/+0
| | | | | | | | | | | This isn't fully tested as yet, in particular I'm not sure that the "foo--unpackaged--1.0.sql" scripts are OK. But it's time to get some buildfarm cycles on it. sepgsql is not converted to an extension, mainly because it seems to require a very nonstandard installation process. Dimitri Fontaine and Tom Lane
* Support LIKE and ILIKE index searches via contrib/pg_trgm indexes.Tom Lane2011-01-311-6/+10
| | | | | | | | | | Unlike Btree-based LIKE optimization, this works for non-left-anchored search patterns. The effectiveness of the search depends on how many trigrams can be extracted from the pattern. (The worst case, with no trigrams, degrades to a full-table scan, so this isn't a panacea. But it can be very useful.) Alexander Korotkov, reviewed by Jan Urbanski
* Add KNNGIST support to contrib/pg_trgm.Tom Lane2010-12-041-1/+20
| | | | Teodor Sigaev, with some revision by Tom
* Remove useless whitespace at end of linesPeter Eisentraut2010-11-231-1/+1
|
* Remove cvs keywords from all files.Magnus Hagander2010-09-201-1/+1
|
* Mark contrib's GiST and GIN opclass support functions as STRICT, for safety.Tom Lane2009-06-111-11/+11
| | | | | (Note: GiST penalty functions could possibly be non-strict, but none are at present.)
* Adjust the APIs for GIN opclass support functions to allow the extractQuery()Tom Lane2009-03-251-6/+6
| | | | | | | | | | | | | | method to pass extra data to the consistent() and comparePartial() methods. This is the core infrastructure needed to support the soon-to-appear contrib/btree_gin module. The APIs are still upward compatible with the definitions used in 8.3 and before, although *not* with the previous 8.4devel function definitions. catversion bump for changes in pg_proc entries (although these are just cosmetic, since GIN doesn't actually look at the function signature before calling it...) Teodor Sigaev and Oleg Bartunov
* Push index operator lossiness determination down to GIST/GIN opclassTom Lane2008-04-141-6/+6
| | | | | | | | | | | "consistent" functions, and remove pg_amop.opreqcheck, as per recent discussion. The main immediate benefit of this is that we no longer need 8.3's ugly hack of requiring @@@ rather than @@ to test weight-using tsquery searches on GIN indexes. In future it should be possible to optimize some other queries better than is done now, by detecting at runtime whether the index match is exact or not. Tom Lane, after an idea of Heikki's, and with some help from Teodor.
* Fix completely-bogus volatility markings on pg_trgm functions.Tom Lane2007-12-091-4/+4
|
* Add CVS version labels to all install/uninstall scripts.Bruce Momjian2007-11-131-0/+2
|
* Make /contrib install/uninstall script consistent:Bruce Momjian2007-11-111-26/+23
| | | | | | | | | | | | remove transactions use create or replace function make formatting consistent set search patch on first line Add documentation on modifying *.sql to set the search patch, and mention that major upgrades should still run the installation scripts. Some of these issues were spotted by Tom today.
* Support functions for index opclasses should be immutable.Tom Lane2007-09-301-17/+17
| | | | Found by running opr_sanity on contrib modules.
* Add GIN support for pg_trgm. From Guillaume Smet <guillaume.smet@gmail.com>Teodor Sigaev2007-03-141-3/+29
| | | | with minor editorization by me.
* Clean up CREATE FUNCTION syntax usage in contrib and elsewhere, inPeter Eisentraut2006-02-271-14/+14
| | | | | particular get rid of single quotes around language names and old WITH () construct.
* trgm - Trigram matching for PostgreSQLTeodor Sigaev2004-05-311-0/+107
-------------------------------------- The pg_trgm contrib module provides functions and index classes for determining the similarity of text based on trigram matching.