summaryrefslogtreecommitdiff
path: root/contrib/pg_trgm
Commit message (Collapse)AuthorAgeFilesLines
* Support "make check" in contribPeter Eisentraut2011-04-251-0/+2
| | | | | | | | | | | | | | Added a new option --extra-install to pg_regress to arrange installing the respective contrib directory into the temporary installation. This is currently not yet supported for Windows MSVC builds. Updated the .gitignore files for contrib modules to ignore the leftovers of a temp-install check run. Changed the exit status of "make check" in a pgxs build (which still does nothing) to 0 from 1. Added "make check" in contrib to top-level "make check-world".
* pgindent run before PG 9.1 beta 1.Bruce Momjian2011-04-104-38/+46
|
* Fix contrib/pg_trgm to have smoother updates from 9.0.Tom Lane2011-02-173-15/+83
| | | | | | | | | | | | | | | Take care of some loose ends in the update-from-unpackaged script, and apply some ugly hacks to ensure that it produces the same catalog state as the fresh-install script. Per discussion, this seems like a safer plan than having two different catalog states that both call themselves "pg_trgm 1.0", even if it's not immediately clear that the subtle differences would ever matter. Also, fix the stub function gin_extract_trgm() so that it works instead of just bleating. Needed because this function will get called during a regular dump and reload, if there are any indexes using its opclass. The user won't have an opportunity to update the extension till later, so telling him to do so is unhelpful.
* Assorted fixups for "unpackaged" conversion scripts.Tom Lane2011-02-131-2/+14
| | | | | | | From first pass of testing. Notably, there seems to be no need for adminpack--unpackaged--1.0.sql because none of the objects that the old module creates would ever be dumped by pg_dump anyway (they are all in pg_catalog).
* Avoid use of CREATE OR REPLACE FUNCTION in extension installation files.Tom Lane2011-02-131-19/+19
| | | | | | | | | | | It was never terribly consistent to use OR REPLACE (because of the lack of comparable functionality for data types, operators, etc), and experimentation shows that it's now positively pernicious in the extension world. We really want a failure to occur if there are any conflicts, else it's unclear what the extension-ownership state of the conflicted object ought to be. Most of the time, CREATE EXTENSION will fail anyway because of conflicts on other object types, but an extension defining only functions can succeed, with bad results.
* Convert contrib modules to use the extension facility.Tom Lane2011-02-138-71/+39
| | | | | | | | | | | 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-318-48/+624
| | | | | | | | | | 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
* Update contrib/pg_trgm for new GIN extractQuery API.Tom Lane2011-01-091-28/+18
| | | | | No actual change in functionality ... just get rid of uselessly complex code to pass the number of keys via extra_data.
* Add KNNGIST support to contrib/pg_trgm.Tom Lane2010-12-048-41/+192
| | | | Teodor Sigaev, with some revision by Tom
* Remove useless whitespace at end of linesPeter Eisentraut2010-11-232-2/+2
|
* Some more gitignore cleanups: cover contrib and PL regression test outputs.Tom Lane2010-09-221-0/+2
| | | | | Also do some further work in the back branches, where quite a bit wasn't covered by Magnus' original back-patch.
* Convert cvsignore to gitignore, and add .gitignore for build targets.Magnus Hagander2010-09-221-0/+1
|
* Remove cvs keywords from all files.Magnus Hagander2010-09-207-7/+7
|
* Remove extra newlines at end and beginning of files, add missing newlinesPeter Eisentraut2010-08-191-1/+0
| | | | at end of files.
* 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.)
* 8.4 pgindent run, with new combined Linux/FreeBSD/MinGW typedef listBruce Momjian2009-06-114-63/+65
| | | | provided by Andrew.
* Blank line Makefile cleanups.Bruce Momjian2009-04-281-2/+1
|
* Adjust the APIs for GIN opclass support functions to allow the extractQuery()Tom Lane2009-03-253-39/+26
| | | | | | | | | | | | | | 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
* Support of multibyte encoding for pg_trgmTeodor Sigaev2008-11-123-88/+161
|
* Add caching of query to GIN/GiST consistent function.Teodor Sigaev2008-07-112-6/+48
| | | | Per performance gripe from nomao.com
* Add $PostgreSQL$ markers to a lot of files that were missing them.Andrew Dunstan2008-05-174-0/+12
| | | | | | | | | | This particular batch was just for *.c and *.h file. The changes were made with the following 2 commands: find . \( \( -name 'libstemmer' -o -name 'expected' -o -name 'ppport.h' \) -prune \) -o \( -name '*.[ch]' \) \( -exec grep -q '\$PostgreSQL' {} \; -o -print \) | while read file ; do head -n 1 < $file | grep -q '^/\*' && echo $file; done | xargs -l sed -i -e '1s/^\// /' -e '1i/*\n * $PostgreSQL:$ \n *' find . \( \( -name 'libstemmer' -o -name 'expected' -o -name 'ppport.h' \) -prune \) -o \( -name '*.[ch]' \) \( -exec grep -q '\$PostgreSQL' {} \; -o -print \) | xargs -l sed -i -e '1i/*\n * $PostgreSQL:$ \n */'
* Push index operator lossiness determination down to GIST/GIN opclassTom Lane2008-04-144-14/+26
| | | | | | | | | | | "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
|
* Run pgindent on remaining files now that LOOPBYTE is a usable macro.Bruce Momjian2007-11-161-9/+9
|
* Modify LOOPBYTE/LOOPBIT macros to be more logical; rather than have theBruce Momjian2007-11-162-29/+26
| | | | | | | for() body passed as a parameter, make the macros act as simple headers to code blocks. This allows pgindent to be run on these files.
* pgindent run for 8.3.Bruce Momjian2007-11-151-18/+18
|
* Fix a few contrib regression test scripts that hadn't gotten the wordTom Lane2007-11-132-3/+12
| | | | | | | about best practice for including the module creation scripts: to wit that you should suppress NOTICE messages. This avoids creating regression failures by adding or removing comment lines in the module scripts.
* Add CVS version labels to all install/uninstall scripts.Bruce Momjian2007-11-133-2/+6
|
* Adjust pg_trgm expected output for new *.sql file.Bruce Momjian2007-11-111-2/+2
|
* Make /contrib install/uninstall script consistent:Bruce Momjian2007-11-112-30/+24
| | | | | | | | | | | | 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.
* Remove references to READMEs from /contrib Makefiles.Bruce Momjian2007-11-101-2/+1
|
* Move most /contrib README files into SGML. Some still need conversionBruce Momjian2007-11-101-144/+0
| | | | or will never be converted.
* Support functions for index opclasses should be immutable.Tom Lane2007-09-301-17/+17
| | | | Found by running opr_sanity on contrib modules.
* Simplify overly-cute array coding to avoid an apparent gcc bug, whichTom Lane2007-07-121-10/+5
| | | | may or may not be harmless. Report from Stefan, patch from Heikki.
* Fix PGXS conventions so that extensions can be built against PostgresTom Lane2007-06-261-2/+3
| | | | | | installations whose pg_config program does not appear first in the PATH. Per gripe from Eddie Stanley and subsequent discussions with Fabien Coelho and others.
* Support varlena fields with single-byte headers and unaligned storage.Tom Lane2007-04-061-2/+20
| | | | | | | | | This commit breaks any code that assumes that the mere act of forming a tuple (without writing it to disk) does not "toast" any fields. While all available regression tests pass, I'm not totally sure that we've fixed every nook and cranny, especially in contrib. Greg Stark with some help from Tom Lane
* Add GIN support for pg_trgm. From Guillaume Smet <guillaume.smet@gmail.com>Teodor Sigaev2007-03-148-5/+1256
| | | | with minor editorization by me.
* Fix up several contrib modules that were using varlena datatypes in ↵Tom Lane2007-02-283-15/+17
| | | | | | | not-so-obvious ways. I'm not totally sure that I caught everything, but at least now they pass their regression tests with VARSIZE/SET_VARSIZE defined to reverse byte order.
* Replace direct assignments to VARATT_SIZEP(x) with SET_VARSIZE(x, len).Tom Lane2007-02-271-1/+1
| | | | | | | | | | | Get rid of VARATT_SIZE and VARATT_DATA, which were simply redundant with VARSIZE and VARDATA, and as a consequence almost no code was using the longer names. Rename the length fields of struct varlena and various derived structures to catch anyplace that was accessing them directly; and clean up various places so caught. In itself this patch doesn't change any behavior at all, but it is necessary infrastructure if we hope to play any games with the representation of varlena headers. Greg Stark and Tom Lane
* Remove useless CPPFLAGS.Peter Eisentraut2007-02-091-3/+1
|
* Add $PostgreSQL$ marker to contrib makefiles.Peter Eisentraut2007-02-091-4/+1
|
* Squelch some VC++ compiler warnings. Mark float literals with the "f"Neil Conway2007-01-261-1/+1
| | | | | | | suffix, to distinguish them from doubles. Make some function declarations and definitions use the "const" qualifier for arguments consistently. Ignore warning 4102 ("unreferenced label"), because such warnings are always emitted by bison-generated code. Patch from Magnus Hagander.
* pgindent run for 8.2.Bruce Momjian2006-10-041-4/+4
|
* Fix a passel of recently-committed violations of the rule 'thou shaltTom Lane2006-07-141-2/+0
| | | | | have no other gods before c.h'. Also remove some demonstrably redundant #include lines, mostly of <errno.h> which was added to c.h years ago.
* Alphabetically order reference to include files, "S"-"Z".Bruce Momjian2006-07-111-1/+1
|
* ChangesTeodor Sigaev2006-06-281-2/+2
| | | | | | | | | | | | | | | | | | | | * new split algorithm (as proposed in http://archives.postgresql.org/pgsql-hackers/2006-06/msg00254.php) * possible call pickSplit() for second and below columns * add spl_(l|r)datum_exists to GIST_SPLITVEC - pickSplit should check its values to use already defined spl_(l|r)datum for splitting. pickSplit should set spl_(l|r)datum_exists to 'false' (if they was 'true') to signal to caller about using spl_(l|r)datum. * support for old pickSplit(): not very optimal but correct split * remove 'bytes' field from GISTENTRY: in any case size of value is defined by it's type. * split GIST_SPLITVEC to two structures: one for using in picksplit and second - for internal use. * some code refactoring * support of subsplit to rtree opclasses TODO: add support of subsplit to contrib modules
* Magic blocks don't do us any good unless we use 'em ... so install oneTom Lane2006-05-301-0/+2
| | | | in every shared library.
* Fix a number of syntax errors in contrib modules' uninstall scripts.Neil Conway2006-03-131-6/+2
| | | | | | | | | Most of the changes add the mandatory USING clause to DROP OPERATOR CLASS statements. DROP TYPE is now DROP TYPE CASCADE; without CASCADE a DROP TYPE fails due to the circular dependency on the type's I/O functions. The DROP FUNCTION statements for the I/O functions have been removed, as DROP TYPE CASCADE removes them automatically. Patch from Michael Fuhr.
* This patch makes the error message strings throughout the backendNeil Conway2006-03-012-3/+3
| | | | | | | | more compliant with the error message style guide. In particular, errdetail should begin with a capital letter and end with a period, whereas errmsg should not. I also fixed a few related issues in passing, such as fixing the repeated misspelling of "lexeme" in contrib/tsearch2 (per Tom's suggestion).
* 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.
View Lorry Controller Status