7 Commits (99fd5cbd410c29381d2ffdfd98705c68fe99fbe3)

Author	SHA1	Message	Date
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