aboutsummaryrefslogtreecommitdiff
path: root/contrib/intarray
Commit message (Collapse)AuthorAge
* Detoast query in g_intbig_consistent and copy query in g_int_consistent.Teodor Sigaev2006-04-03
| | | | Minor cleanups.
* Replace bitwise looping with bytewise looping in hemdistsign andTom Lane2006-01-20
| | | | | | | sizebitvec of tsearch2, as well as identical code in several other contrib modules. This provided about a 20X speedup in building a large tsearch2 index ... didn't try to measure its effects for other operations. Thanks to Stephan Vollmer for providing a test case.
* Standard pgindent run for 8.1.Bruce Momjian2005-10-15
|
* Optimize benchmark query and update benchmark's results.Teodor Sigaev2005-10-03
|
* PGXS should be set with := not =, as specified in the documentation,Tom Lane2005-09-27
| | | | to avoid useless multiple executions of pg_config.
* Clean up possibly-uninitialized-variable warnings reported by gcc 4.x.Tom Lane2005-09-24
|
* Add parentheses to macros when args are used in computations. WithoutBruce Momjian2005-05-25
| | | | them, the executation behavior could be unexpected.
* Add intset() to READMETeodor Sigaev2005-01-27
|
* Standardize on using the Min, Max, and Abs macros that are in our c.h file,Tom Lane2004-10-21
| | | | | | getting rid of numerous ad-hoc versions that have popped up in various places. Shortens code and avoids conflict with Windows min() and max() macros.
* Pgindent run for 8.0.Bruce Momjian2004-08-29
|
* > Please find enclose a submission to fix these problems.Bruce Momjian2004-08-20
| | | | | | | | | | | | | | | | | | | | | | > > The patch adds missing the "libpgport.a" file to the installation under > "install-all-headers". It is needed by some contribs. I install the > library in "pkglibdir", but I was wondering whether it should be "libdir"? > I was wondering also whether it would make sense to have a "libpgport.so"? > > It fixes various macros which are used by contrib makefiles, especially > libpq_*dir and LDFLAGS when used under PGXS. It seems to me that they are > needed to > > It adds the ability to test and use PGXS with contribs, with "make > USE_PGXS=1". Without the macro, this is exactly as before, there should be > no difference, esp. wrt the vpath feature that seemed broken by previous > submission. So it should not harm anybody, and it is useful at least to me. > > It fixes some inconsistencies in various contrib makefiles > (useless override, ":=" instead of "="). Fabien COELHO
* Cleanup vectors of GISTENTRY and eliminate problem with 64-bit strict-alignedTeodor Sigaev2004-03-30
| | | | | | 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-08
| | | | | datatype; the generic array comparators added in 7.4 supersede this. Per report and patch from Korea PostgreSQL Users' Group.
* $Header: -> $PostgreSQL Changes ...PostgreSQL Daemon2003-11-29
|
* pgindent run.Bruce Momjian2003-08-04
|
* Update contrib regression tests for recent error message editing.Tom Lane2003-08-01
|
* Error message editing in contrib (mostly by Joe Conway --- thanks Joe!)Tom Lane2003-07-24
|
* Update expected file to match new _int.sql.Tom Lane2003-06-11
|
* Add missing intarray files.Bruce Momjian2003-06-11
|
* Changes:Bruce Momjian2003-06-11
| | | | | | | | | | | 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
* Make debug_ GUC varables output DEBUG1 rather than LOG, and mention inBruce Momjian2003-05-27
| | | | | docs that CLIENT/LOG_MIN_MESSAGES now controls debug_* output location. Doc changes included.
* Fix failure when uniq-ifying an array of zero elements.Tom Lane2003-05-16
| | | | Teodor Sigaev
* Backend support for autocommit removed, per recent discussions. TheTom Lane2003-05-14
| | | | | | 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.
* This patch fixes a bunch of spelling mistakes in comments throughout theTom Lane2003-03-10
| | | | | | PostgreSQL source code. Neil Conway
* Small fix in documentation and some examples of usage. Please, apply toBruce Momjian2002-12-27
| | | | | | 7.3 and current CVS Oleg Bartunov
* Add new palloc0 call as merge of palloc and MemSet(0).Bruce Momjian2002-11-13
|
* Back out use of palloc0 in place if palloc/MemSet. Seems constant lenBruce Momjian2002-11-11
| | | | to MemSet is a performance boost.
* Merge palloc()/MemSet(0) calls into a single palloc0() call.Bruce Momjian2002-11-10
|
* Ooops, forgot to fix contrib regression tests for WARNING/NOTICE change.Tom Lane2002-11-01
|
* SET autocommit no longer needed in /contrib because pg_regress.sh doesBruce Momjian2002-10-21
| | | | it automatically now on regression session startup.
* Update /contrib for "autocommit TO 'on'".Bruce Momjian2002-10-18
| | | | | | | | | | Create objects in public schema. Make spacing/capitalization consistent. Remove transaction block use for object creation. Remove unneeded function GRANTs.
* This is small README fix for contrib/intarray. Thank you.Bruce Momjian2002-10-03
| | | | Teodor Sigaev
* Clean up mess from duplicate patches.Tom Lane2002-09-14
|
* > intarray and ltree both seem to be mapping their own declarations ontoBruce Momjian2002-09-12
| | | | | | | | | | > arrays using largely-similar code. But while intarray fails its > regression test, I find ltree still passes. So I'm confused about what > that code is really doing and don't want to touch it. Please, apply attached patch, it solves the problem. Teodor Sigaev
* The attached small patch fixes the cause of the regression test failureBruce Momjian2002-09-12
| | | | | | | | | | for contrib/intarray. The cause was that the library uses its own function to construct a new array, new_intArrayType, and that function did not set the new array struct attribute elemtype. Joe Conway
* pgindent run.Bruce Momjian2002-09-04
|
* I checked all the previous string handling errors and most of them wereBruce Momjian2002-09-02
| | | | | | | | | | | | | | | already fixed by You. However there were a few left and attached patch should fix the rest of them. I used StringInfo only in 2 places and both of them are inside debug ifdefs. Only performance penalty will come from using strlen() like all the other code does. I also modified some of the already patched parts by changing snprintf(buf, 2 * BUFSIZE, ... style lines to snprintf(buf, sizeof(buf), ... where buf is an array. Jukka Holappa
* Update contrib regression tests for OPAQUE datatype changes.Tom Lane2002-08-23
|
* Add a bunch of pseudo-types to replace the behavior formerly associatedTom Lane2002-08-22
| | | | | | 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-10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-29
| | | | | | | 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-07
| | | | | | | | | | 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-17
| | | | | | | 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.
* Change made to elog:Bruce Momjian2002-03-06
| | | | | | | | | | | | | | | | | | | o Change all current CVS messages of NOTICE to WARNING. We were going to do this just before 7.3 beta but it has to be done now, as you will see below. o Change current INFO messages that should be controlled by client_min_messages to NOTICE. o Force remaining INFO messages, like from EXPLAIN, VACUUM VERBOSE, etc. to always go to the client. o Remove INFO from the client_min_messages options and add NOTICE. Seems we do need three non-ERROR elog levels to handle the various behaviors we need for these messages. Regression passed.
* Repair some problems in GIST-index contrib modules. Patch fromTom Lane2002-02-07
| | | | Teodor Sigaev <teodor@stack.net>.
* Remove bogus pg_amop insertion commands, per discussion of 25-Oct.Tom Lane2001-11-24
| | | | | No change in results of script, but perhaps less confusion for people reading it.
* 1. Implemented binary search in arrayBruce Momjian2001-10-04
| | | | Oleg Bartunov
* Changes:Tom Lane2001-09-30
| | | | | | | 1. gist__int_ops is now without lossy 2. added sort entry in picksplit Oleg Bartunov
* Update required due to recent changes in FigureColname.Tom Lane2001-09-30
|
* please apply attached patch to current CVS.Bruce Momjian2001-09-23
| | | | | | | | | | | Changes: 1. Added support for boolean queries (indexable operator @@, looks like a @@ '1|(2&3)' 2. Some code cleanup and optimization Regards, Oleg
generated by cgit v1.2.3 (git 2.25.1) at 2025-05-31 09:34:31 +0000