pgsql/ ontrib/btree_gist/btree_gist.sql.in ont ...
От | tgl@postgresql.org (Tom Lane) |
---|---|
Тема | pgsql/ ontrib/btree_gist/btree_gist.sql.in ont ... |
Дата | |
Msg-id | 20020417205757.321094759B3@postgresql.org обсуждение исходный текст |
Список | pgsql-committers |
CVSROOT: /cvsroot Module name: pgsql Changes by: tgl@postgresql.org 02/04/17 16:57:57 Modified files: contrib/btree_gist: btree_gist.sql.in contrib/cube : cube.sql.in contrib/intarray: _int.sql.in contrib/rtree_gist: rtree_gist.sql.in contrib/seg : seg.sql.in contrib/tsearch: tsearch.sql.in doc/src/sgml : xindex.sgml src/backend/access/index: indexam.c src/backend/bootstrap: bootparse.y src/backend/catalog: indexing.c namespace.c src/backend/commands: indexcmds.c src/backend/nodes: copyfuncs.c equalfuncs.c outfuncs.c src/backend/parser: analyze.c gram.y src/backend/utils/cache: syscache.c src/include/catalog: catversion.h indexing.h namespace.h pg_opclass.h src/include/nodes: parsenodes.h src/include/utils: syscache.h src/tutorial : complex.source Log message: 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.
В списке pgsql-committers по дате отправления: