12 Commits (02490d4692c46bee3e9279e79c5d07c576d2a32c)

Author	SHA1	Message	Date
Tom Lane	156475a589	Revert my patch of 2009-04-04 that removed contrib/intarray's definitions of ... the <@ and @> operators. These are not in fact equivalent to the built-in anyarray operators of the same names, because they have different behavior for empty arrays, namely they don't think empty arrays are contained in anything. That is mathematically wrong, no doubt, but until we can persuade GIN indexes to implement the mathematical definition we should probably not change this. Another reason for not changing it now is that we can't yet ensure the opclasses will be updated correctly in a dump-and-reload upgrade. Per recent discussions.	17 years ago
Tom Lane	65e758a4d3	Remove contrib/intarray's definitions of the <@ and @> operators, so that they ... don't cause confusion with the built-in anyarray versions of those operators. Adjust the module's index opclasses to support the built-in operators in place of the private ones. The private implementations are still available under their historical names @ and ~, so no functionality is lost. Some quick testing suggests that they offer no real benefit over the core operators, however. Per a complaint from Rusty Conover.	17 years ago
Tom Lane	87b8db3774	Adjust the APIs for GIN opclass support functions to allow the extractQuery() ... method to pass extra data to the consistent() and comparePartial() methods. This is the core infrastructure needed to support the soon-to-appear contrib/btree_gin module. The APIs are still upward compatible with the definitions used in 8.3 and before, although *not* with the previous 8.4devel function definitions. catversion bump for changes in pg_proc entries (although these are just cosmetic, since GIN doesn't actually look at the function signature before calling it...) Teodor Sigaev and Oleg Bartunov	17 years ago
Tom Lane	9b5c8d45f6	Push index operator lossiness determination down to GIST/GIN opclass ... "consistent" functions, and remove pg_amop.opreqcheck, as per recent discussion. The main immediate benefit of this is that we no longer need 8.3's ugly hack of requiring @@@ rather than @@ to test weight-using tsquery searches on GIN indexes. In future it should be possible to optimize some other queries better than is done now, by detecting at runtime whether the index match is exact or not. Tom Lane, after an idea of Heikki's, and with some help from Teodor.	18 years ago
Bruce Momjian	33e2e02493	Add CVS version labels to all install/uninstall scripts.	18 years ago
Bruce Momjian	926bbab448	Make /contrib install/uninstall script consistent: ... 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.	18 years ago
Tom Lane	2d6cb170d4	Remove ill-considered (not to mention undocumented) attempt to make ... contrib/intarray's GIN opclass override the built-in default. Per bug #3048 and other complaints.	19 years ago
Tom Lane	a78fcfb512	Restructure operator classes to allow improved handling of cross-data-type ... 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.	19 years ago
Tom Lane	684ad6a92f	Rename contrib contains/contained-by operators to @> and <@, per discussion.	20 years ago
Teodor Sigaev	5320c6cf6b	Make GIN opclass worked with intarray extensions	20 years ago
Neil Conway	48fb696753	Fix a number of syntax errors in contrib modules' uninstall scripts. ... Most of the changes add the mandatory USING clause to DROP OPERATOR CLASS statements. DROP TYPE is now DROP TYPE CASCADE; without CASCADE a DROP TYPE fails due to the circular dependency on the type's I/O functions. The DROP FUNCTION statements for the I/O functions have been removed, as DROP TYPE CASCADE removes them automatically. Patch from Michael Fuhr.	20 years ago
Peter Eisentraut	fe83b3ebc6	contrib uninstall scripts ... by David Fetter	20 years ago