From 27a54ae282d74ee471a5b34d136fe3d4f894a9de Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Wed, 17 Apr 2002 20:57:57 +0000 Subject: 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. --- contrib/cube/cube.sql.in | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'contrib/cube/cube.sql.in') diff --git a/contrib/cube/cube.sql.in b/contrib/cube/cube.sql.in index 00994d39a0..a1a78ca9f5 100644 --- a/contrib/cube/cube.sql.in +++ b/contrib/cube/cube.sql.in @@ -212,10 +212,12 @@ CREATE FUNCTION g_cube_same(cube, cube, opaque) RETURNS opaque -- register the default opclass for indexing -INSERT INTO pg_opclass (opcamid, opcname, opcintype, opcdefault, opckeytype) +INSERT INTO pg_opclass (opcamid, opcname, opcnamespace, opcowner, opcintype, opcdefault, opckeytype) VALUES ( (SELECT oid FROM pg_am WHERE amname = 'gist'), 'gist_cube_ops', + (SELECT oid FROM pg_namespace WHERE nspname = 'pg_catalog'), + 1, -- UID of superuser is hardwired to 1 as of PG 7.3 (SELECT oid FROM pg_type WHERE typname = 'cube'), true, 0); -- cgit v1.2.1