summaryrefslogtreecommitdiff
path: root/contrib/seg
Commit message (Collapse)AuthorAgeFilesLines
* Cleanup vectors of GISTENTRY and eliminate problem with 64-bit strict-alignedTeodor Sigaev2004-03-302-15/+15
| | | | | | boxes. Change interface to user-defined GiST support methods union and picksplit. Now instead of bytea struct it used special GistEntryVector structure.
* Localize our dependencies on the way to create NAN or INFINITY.Tom Lane2004-03-152-8/+4
| | | | Per recent proposal to pghackers.
* Add %option nodefault to all our flex lexers. Fix a couple of rule gapsTom Lane2004-02-241-1/+2
| | | | | | exposed thereby. AFAICT these would not lead to any worse problems than junk emitted on the backend's stdout, but we should have the option to catch possible worse errors in future.
* $Header: -> $PostgreSQL Changes ...PostgreSQL Daemon2003-11-291-1/+1
|
* Make contrib/seg work with flex 2.5.31. Fix it up to have a realTom Lane2003-09-149-190/+115
| | | | btree operator class, too, since in PG 7.4 you can't GROUP without one.
* Update contrib regression tests for recent error message editing.Tom Lane2003-08-011-1/+1
|
* Error message editing in contrib (mostly by Joe Conway --- thanks Joe!)Tom Lane2003-07-244-23/+38
|
* Ensure that in all flex lexers that are part of the backend, aTom Lane2003-05-291-0/+3
| | | | | | | yy_fatal_error() call results in elog(ERROR) not exit(). This was already fixed in the main lexer and plpgsql, but extend same technique to all the other dot-l files. Also, on review of the possible calls to yy_fatal_error(), it seems safe to use elog(ERROR) not elog(FATAL).
* Fix various recent build and regression-test problems in contrib/.Tom Lane2003-05-141-8/+2
| | | | Includes fixes from Joe Conway.
* Backend support for autocommit removed, per recent discussions. TheTom Lane2003-05-142-11/+9
| | | | | | 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.
* Tweak bison build rules so that we get the same error messages fromTom Lane2003-01-311-2/+8
| | | | | | | | bison 1.875 and later as we did from earlier bison releases. Eventually we will probably want to adopt the newer message spelling ... but not yet. Per recent discussion on pgpatches. Note: I didn't change the build rules for bootstrap, ecpg, or plpgsql grammars, since these do not affect regression test results.
* Fix a dozen or so places that were passing unpredictable data stringsTom Lane2002-11-221-2/+2
| | | | | as elog format strings. Hai-Chen Tu pointed out the problem in contrib/dbmirror, but it wasn't the only such error.
* Remove no-longer-needed inclusions to improve backward compatibilityTom Lane2002-11-071-2/+1
| | | | with older bison versions.
* Ooops, forgot to fix contrib regression tests for WARNING/NOTICE change.Tom Lane2002-11-011-2/+2
|
* Arrange to compile flex output files as inclusions into other filesTom Lane2002-11-012-3/+6
| | | | | | | | (usually bison output files), not as standalone files. This hack works around flex's insistence on including <stdio.h> before we are able to include postgres.h; postgres.h will already be read before the compiler starts to read the flex output file. Needed for largefile support on some platforms.
* SET autocommit no longer needed in /contrib because pg_regress.sh doesBruce Momjian2002-10-211-1/+0
| | | | it automatically now on regression session startup.
* Update /contrib for "autocommit TO 'on'".Bruce Momjian2002-10-183-102/+198
| | | | | | | | | | Create objects in public schema. Make spacing/capitalization consistent. Remove transaction block use for object creation. Remove unneeded function GRANTs.
* Remove extraneous | ... while bison 1.28 doesn't object, newer versionsTom Lane2002-09-221-1/+0
| | | | do.
* I haven't seen any objections, so here is a patch. It removes "#defineTom Lane2002-09-222-8/+7
| | | | | | | | YYERROR_VERBOSE" from contrib/cube and contrib/seg, and adjusts the expected output accordingly. Hopefully this will consistently pass across multiple bison versions. Joe Conway
* Be careful to include postgres.h *before* any system headers, to ensureTom Lane2002-09-051-2/+2
| | | | | | that the right flavors of largefile-related definitions are seen. Most of these changes are probably unnecessary, but better safe than sorry.
* I checked all the previous string handling errors and most of them wereBruce Momjian2002-09-021-2/+3
| | | | | | | | | | | | | | | 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-231-0/+2
|
* Add a bunch of pseudo-types to replace the behavior formerly associatedTom Lane2002-08-222-26/+18
| | | | | | 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 ...
* Replace ad-hoc insertions into pg_opclass and friends with CREATETom Lane2002-07-301-157/+23
| | | | OPERATOR CLASS commands. Further tweaking of documentation for same.
* Use Max/Min macros, not MAX/MIN, to eliminate portability issues.Tom Lane2002-07-301-11/+7
|
* Since we're depending on %option noyywrap in the main scanner now,Tom Lane2002-07-301-2/+6
| | | | | we may as well use it in all our flex files. Make all the flex files have a consistent set of options.
* Opclasses live in namespaces. I also took the opportunity to createTom Lane2002-04-171-1/+3
| | | | | | | 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.
* Make the yacc rules safe for parallel make. See discussion on pgsql-patchesPeter Eisentraut2001-11-161-2/+4
| | | | and comment in src/backend/parser/Makefile for the technical details.
* New pgindent run with fixes suggested by Tom. Patch manually reviewed,Bruce Momjian2001-11-051-1/+1
| | | | initdb/regression tests pass.
* pgindent run on all C files. Java run to follow. initdb/regressionBruce Momjian2001-10-251-10/+4
| | | | tests pass.
* To fix the perpetually broken makefiles in the contrib tree, I havePeter Eisentraut2001-09-061-63/+8
| | | | | | written a generic framework of rules that the contrib makefiles can use instead of writing their own each time. You only need to set a few variables and off you go.
* Restructure pg_opclass, pg_amop, and pg_amproc per previous discussions inTom Lane2001-08-211-65/+98
| | | | | | | | | | | | | | | | | | | | 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.
* 1. null-safe interface to GiSTBruce Momjian2001-08-101-19/+19
| | | | | | | | | | | | | | (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
* The attached patch enables the contrib subtree to build cleanly underBruce Momjian2001-06-182-1/+6
| | | | | | | | | | | | | | | | | | | | | Cygwin with the possible exception of mSQL-interface. Since I don't have mSQL installed, I skipped this tool. Except for dealing with a missing getopt.h (oid2name) and HUGE (seg), the bulk of the patch uses the standard PostgreSQL approach to deal with Windows DLL issues. I tested the build aspect of this patch under Cygwin and Linux without any ill affects. Note that I did not actually attempt to test the code for functionality. The procedure to apply the patch is as follows: $ # save the attachment as /tmp/contrib.patch $ # change directory to the top of the PostgreSQL source tree $ patch -p0 </tmp/contrib.patch Jason
* Updates to make GIST work with multi-key indexes (from Oleg BartunovTom Lane2001-05-311-34/+27
| | | | | and Teodor Sigaev). Declare key values as Datum where appropriate, rather than char* (Tom Lane).
* pgindent run. Make it all clean.Bruce Momjian2001-03-224-716/+805
|
* Make sure -L and -I's for our source tree are always before system includePeter Eisentraut2001-02-201-2/+2
| | | | or library directories on the command line.
* Only look for bison as YACC; other yaccs need to be selected explicitly.Peter Eisentraut2001-02-101-1/+5
| | | | | When no suitable YACC is configured, supply useful informational messages to users. (Same way flex has been handled for a while.)
* Gene Selkov's SEG datatype (GiST example code)Tom Lane2000-12-1114-0/+6076
View Lorry Controller Status