summaryrefslogtreecommitdiff
path: root/contrib/intarray/_int.sql.in
Commit message (Collapse)AuthorAgeFilesLines
* 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-53/+48
| | | | | | | | | | | | 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-291-45/+45
| | | | Found by running opr_sanity on contrib modules.
* Remove ill-considered (not to mention undocumented) attempt to makeTom Lane2007-09-141-5/+1
| | | | | contrib/intarray's GIN opclass override the built-in default. Per bug #3048 and other complaints.
* Restructure operator classes to allow improved handling of cross-data-typeTom Lane2006-12-231-3/+3
| | | | | | | | | | | | | | | | cases. Operator classes now exist within "operator families". While most families are equivalent to a single class, related classes can be grouped into one family to represent the fact that they are semantically compatible. Cross-type operators are now naturally adjunct parts of a family, without having to wedge them into a particular opclass as we had done originally. This commit restructures the catalogs and cleans up enough of the fallout so that everything still works at least as well as before, but most of the work needed to actually improve the planner's behavior will come later. Also, there are not yet CREATE/DROP/ALTER OPERATOR FAMILY commands; the only way to create a new family right now is to allow CREATE OPERATOR CLASS to make one by default. I owe some more documentation work, too. But that can all be done in smaller pieces once this infrastructure is in place.
* Rename contrib contains/contained-by operators to @> and <@, per discussion.Tom Lane2006-09-101-20/+45
|
* Make GIN opclass worked with intarray extensionsTeodor Sigaev2006-05-031-0/+34
|
* Clean up CREATE FUNCTION syntax usage in contrib and elsewhere, inPeter Eisentraut2006-02-271-43/+44
| | | | | particular get rid of single quotes around language names and old WITH () construct.
* Cleanup vectors of GISTENTRY and eliminate problem with 64-bit strict-alignedTeodor Sigaev2004-03-301-4/+4
| | | | | | boxes. Change interface to user-defined GiST support methods union and picksplit. Now instead of bytea struct it used special GistEntryVector structure.
* Remove broken (and unnecessary) definition of operator <> for _int4Tom Lane2004-01-081-11/+11
| | | | | datatype; the generic array comparators added in 7.4 supersede this. Per report and patch from Korea PostgreSQL Users' Group.
* Changes:Bruce Momjian2003-06-111-4/+22
| | | | | | | | | | | 1 intarray: bugfix for int[]-int[] operation 2 intarray: split _int.c to several files (_int.c now is unused) 3 ntarray (gist__intbig_ops opclass): use special type for index storage 4 ltree (gist__ltree_ops opclass), intarray (gist__intbig_ops): optimize GiST's penalty and picksplit interface functions, now use Hemming distance. Teodor Sigaev
* Backend support for autocommit removed, per recent discussions. TheTom Lane2003-05-141-2/+0
| | | | | | only remnant of this failed experiment is that the server will take SET AUTOCOMMIT TO ON. Still TODO: provide some client-side autocommit logic in libpq.
* Update /contrib for "autocommit TO 'on'".Bruce Momjian2002-10-181-115/+246
| | | | | | | | | | Create objects in public schema. Make spacing/capitalization consistent. Remove transaction block use for object creation. Remove unneeded function GRANTs.
* Add a bunch of pseudo-types to replace the behavior formerly associatedTom Lane2002-08-221-32/+32
| | | | | | with OPAQUE, as per recent pghackers discussion. I still want to do some more work on the 'cstring' pseudo-type, but I'm going to commit the bulk of the changes now before the tree starts shifting under me ...
* August 6, 2002Bruce Momjian2002-08-101-0/+75
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1. Reworked patch from Andrey Oktyabrski (ano@spider.ru) with functions: icount, sort, sort_asc, uniq, idx, subarray operations: #, +, -, |, & FUNCTIONS: int icount(int[]) - the number of elements in intarray int[] sort(int[], 'asc' | 'desc') - sort intarray int[] sort(int[]) - sort in ascending order int[] sort_asc(int[]),sort_desc(int[]) - shortcuts for sort int[] uniq(int[]) - returns unique elements int idx(int[], int item) - returns index of first intarray matching element to item, or '0' if matching failed. int[] subarray(int[],int START [, int LEN]) - returns part of intarray starting from element number START (from 1) and length LEN. OPERATIONS: int[] && int[] - overlap - returns TRUE if arrays has at least one common elements. int[] @ int[] - contains - returns TRUE if left array contains right array int[] ~ int[] - contained - returns TRUE if left array is contained in right array # int[] - return the number of elements in array int[] + int - push element to array ( add to end of array) int[] + int[] - merge of arrays (right array added to the end of left one) int[] - int - remove entries matched by right argument from array int[] - int[] - remove left array from right int[] | int - returns intarray - union of arguments int[] | int[] - returns intarray as a union of two arrays int[] & int[] - returns intersection of arrays Oleg Bartunov
* Implement CREATE/DROP OPERATOR CLASS. Work still remains: need moreTom Lane2002-07-291-262/+35
| | | | | | | documentation (xindex.sgml should be rewritten), need to teach pg_dump about it, need to update contrib modules that currently build pg_opclass entries by hand. Original patch by Bill Studenmund, grammar adjustments and general update for 7.3 by Tom Lane.
* Please apply attached patch to contrib/intarray (7.2, 7.3).Bruce Momjian2002-06-071-1/+10
| | | | | | | | | | Fixed bug with '=' operator for gist__int_ops and define '=' operator for gist__intbig_ops opclass. Now '=' operator is consistent with standard 'array' type. Thanks Achilleus Mantzios for bug report and suggestion. Oleg Bartunov
* Opclasses live in namespaces. I also took the opportunity to createTom Lane2002-04-171-2/+6
| | | | | | | an 'opclass owner' column in pg_opclass. Nothing is done with it at present, but since there are plans to invent a CREATE OPERATOR CLASS command soon, we'll probably want DROP OPERATOR CLASS too, which suggests that a notion of ownership would be a good idea.
* Remove bogus pg_amop insertion commands, per discussion of 25-Oct.Tom Lane2001-11-241-16/+0
| | | | | No change in results of script, but perhaps less confusion for people reading it.
* Changes:Tom Lane2001-09-301-6/+6
| | | | | | | 1. gist__int_ops is now without lossy 2. added sort entry in picksplit Oleg Bartunov
* please apply attached patch to current CVS.Bruce Momjian2001-09-231-6/+86
| | | | | | | | | | | Changes: 1. Added support for boolean queries (indexable operator @@, looks like a @@ '1|(2&3)' 2. Some code cleanup and optimization Regards, Oleg
* Update GiST for new pg_opclass arrangement (finally a clean solutionTom Lane2001-08-221-3/+3
| | | | | | for haskeytype). Update GiST contrib modules too. Add linear-time split algorithm for R-tree GiST opclass. From Oleg Bartunov and Teodor Sigaev.
* Restructure pg_opclass, pg_amop, and pg_amproc per previous discussions inTom Lane2001-08-211-93/+145
| | | | | | | | | | | | | | | | | | | | pgsql-hackers. pg_opclass now has a row for each opclass supported by each index AM, not a row for each opclass name. This allows pg_opclass to show directly whether an AM supports an opclass, and furthermore makes it possible to store additional information about an opclass that might be AM-dependent. pg_opclass and pg_amop now store "lossy" and "haskeytype" information that we previously expected the user to remember to provide in CREATE INDEX commands. Lossiness is no longer an index-level property, but is associated with the use of a particular operator in a particular index opclass. Along the way, IndexSupportInitialize now uses the syscaches to retrieve pg_amop and pg_amproc entries. I find this reduces backend launch time by about ten percent, at the cost of a couple more special cases in catcache.c's IndexScanOK. Initial work by Oleg Bartunov and Teodor Sigaev, further hacking by Tom Lane. initdb forced.
* Make OIDs optional, per discussions in pghackers. WITH OIDS is still theTom Lane2001-08-101-20/+5
| | | | | | | | | | | | default, but OIDS are removed from many system catalogs that don't need them. Some interesting side effects: TOAST pointers are 20 bytes not 32 now; pg_description has a three-column key instead of one. Bugs fixed in passing: BINARY cursors work again; pg_class.relhaspkey has some usefulness; pg_dump dumps comments on indexes, rules, and triggers in a valid order. initdb forced.
* 1. null-safe interface to GiSTBruce Momjian2001-08-101-8/+8
| | | | | | | | | | | | | | (as proposed in http://fts.postgresql.org/db/mw/msg.html?mid=1028327) 2. support for 'pass-by-value' arguments - to test this we used special opclass for int4 with values in range [0-2^15] More testing will be done after resolving problem with index_formtuple and implementation of B-tree using GiST 3. small patch to contrib modules (seg,cube,rtree_gist,intarray) - mark functions as 'isstrict' where needed. Oleg Bartunov
* Update contrib intarray to Jan 25 version.Bruce Momjian2001-03-171-1/+113
|
* commit Oleg and Teodor's RD-tree implementation ... this provides theMarc G. Fournier2001-01-121-0/+211
regression tests for the GiST changes ... this should be integrated into the regular regression tests similar to Vadim's SPI contrib stuff ...
View Lorry Controller Status