Grant SELECT for pg_catalog.pg_dist* to PUBLIC.

Given pg_class et al. are readable by everyone there's little point in
restricting read only access to citus catalogs.
pull/471/head
Andres Freund 2016-04-12 16:00:06 -07:00
parent a5b3dcddb3
commit eae65404d0
2 changed files with 7 additions and 0 deletions

View File

@ -25,3 +25,7 @@ COMMENT ON FUNCTION pg_catalog.master_stage_shard_placement_row(int8, int4, int8
ALTER FUNCTION pg_catalog.citus_drop_trigger() SECURITY DEFINER;
GRANT SELECT ON pg_catalog.pg_dist_partition TO public;
GRANT SELECT ON pg_catalog.pg_dist_shard TO public;
GRANT SELECT ON pg_catalog.pg_dist_shard_placement TO public;

View File

@ -33,6 +33,7 @@ CREATE TABLE citus.pg_dist_partition(
partmethod "char" NOT NULL,
partkey text NOT NULL
);
/* SELECT granted to PUBLIC in upgrade script */
CREATE UNIQUE INDEX pg_dist_partition_logical_relid_index
ON citus.pg_dist_partition using btree(logicalrelid);
ALTER TABLE citus.pg_dist_partition SET SCHEMA pg_catalog;
@ -45,6 +46,7 @@ CREATE TABLE citus.pg_dist_shard(
shardminvalue text,
shardmaxvalue text
);
/* SELECT granted to PUBLIC in upgrade script */
CREATE UNIQUE INDEX pg_dist_shard_shardid_index
ON citus.pg_dist_shard using btree(shardid);
CREATE INDEX pg_dist_shard_logical_relid_index
@ -58,6 +60,7 @@ CREATE TABLE citus.pg_dist_shard_placement(
nodename text NOT NULL,
nodeport int8 NOT NULL
) WITH oids;
/* SELECT granted to PUBLIC in upgrade script */
CREATE UNIQUE INDEX pg_dist_shard_placement_oid_index
ON citus.pg_dist_shard_placement using btree(oid);
CREATE INDEX pg_dist_shard_placement_shardid_index