Re: Foreign table permissions and cloning - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Foreign table permissions and cloning
Date
Msg-id 25637.1303307951@sss.pgh.pa.us
Whole thread Raw
In response to Re: Foreign table permissions and cloning  (Shigeru Hanada <hanada@metrosystems.co.jp>)
Responses Re: Foreign table permissions and cloning  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Shigeru Hanada <hanada@metrosystems.co.jp> writes:
> Attached patch implements along specifications below.  It also includes 
> documents and regression tests.  Some of regression tests might be 
> redundant and removable.

> 1) "GRANT privilege [(column_list)] ON [TABLE] TO role" also work for 
> foreign tables as well as regular tables, if specified privilege was 
> SELECT.  This might seem little inconsistent but I feel natural to use 
> this syntax for SELECT-able objects.  Anyway, such usage can be disabled 
> with trivial fix.

It seems really seriously inconsistent to do that at the same time that
you make other forms of GRANT treat foreign tables as a separate class
of object.  I think if they're going to be a separate class of object,
they should be separate, full stop.  Making them just mostly separate
will confuse people no end.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: pg_dump --binary-upgrade vs. ALTER TYPE ... DROP ATTRIBUTE
Next
From: Pavel Stehule
Date:
Subject: Re: pgbench \for or similar loop