16 Commits (REL8_1_STABLE)

Author	SHA1	Message	Date
Tom Lane	dcf2e1c8c7	Remove the << >> &< and &> operators for contrib/cube, which were ... wrong, but nobody noticed because they were also useless.	21 years ago
Teodor Sigaev	f2c064afcb	Cleanup vectors of GISTENTRY and eliminate problem with 64-bit strict-aligned ... boxes. Change interface to user-defined GiST support methods union and picksplit. Now instead of bytea struct it used special GistEntryVector structure.	22 years ago
Tom Lane	03e47392e0	Make contrib/cube work with flex 2.5.31. Fix it up to have a real ... btree operator class, too, since in PG 7.4 you can't GROUP without one.	23 years ago
Tom Lane	f85f43dfb5	Backend support for autocommit removed, per recent discussions. The ... 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.	23 years ago
Bruce Momjian	80b3513d57	The attached patch provides cube with 4 functions for building cubes ... directly from float8 values. (As opposed to converting the values to strings and then parsing the strings.) The functions are: cube(float8) returns cube cube(float8,float8) returns cube cube(cube,float8) returns cube cube(cube,float8,float8) returns cube Bruno Wolff III	23 years ago
Bruce Momjian	c464212421	When I made the cube(text) function for 7.3, I neglected to add a ... matching create cast command. The attached diff adds a create cast as assignment to cube.sql.in . Bruno Wolff III	23 years ago
Bruce Momjian	aa4c702eac	Update /contrib for "autocommit TO 'on'". ... Create objects in public schema. Make spacing/capitalization consistent. Remove transaction block use for object creation. Remove unneeded function GRANTs.	24 years ago
Bruce Momjian	e57ab04565	This is a comprehensive set of diffs (versus current CVS) that replaces those ... attached to the same message with the Earth Distance patches. Recent changes include changing the subscript in one place I forgot in the previous bugfix patch. A couple of added regression tests, which should help catch this mistake if it reappears. I also put in a limit of 100 dimensions in cube_large and cube_in to prevent making it easy to create very large cubes. Changing one define in cubedata.h will raise the limit if some needs more dimensions. Bruno Wolff III	24 years ago
Bruce Momjian	32784cddf1	The changes I have made are described in CHANGES. This was based on ... diffs to 7.3-devel and may not be applicable to 7.2. I have included a change covered by a previous bugfix patch I submitted (the problem with -.1 not being accepted by cube_in). It does not include a fix for the potential buffer overrun issue I reported for cube_yyerror in cubeparse.y. Bruno Wolff III	24 years ago
Tom Lane	b663f3443b	Add a bunch of pseudo-types to replace the behavior formerly associated ... 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 ...	24 years ago
Tom Lane	e1b040a7c3	Fix potential buffer overrun in cube_out(), per report from ... Bruno Wolff.	24 years ago
Tom Lane	65b6868b13	Replace ad-hoc insertions into pg_opclass and friends with CREATE ... OPERATOR CLASS commands. Further tweaking of documentation for same.	24 years ago
Tom Lane	27a54ae282	Opclasses live in namespaces. I also took the opportunity to create ... 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.	24 years ago
Tom Lane	f933766ba7	Restructure pg_opclass, pg_amop, and pg_amproc per previous discussions in ... 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.	25 years ago
Bruce Momjian	13923be7c8	1. null-safe interface to GiST ... (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	25 years ago
Tom Lane	9892ddf5ee	Gene Selkov's CUBE datatype (GiST example code)	25 years ago