| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Shigeru Hanada <hanada(at)metrosystems(dot)co(dot)jp> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Thom Brown <thom(at)linux(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Foreign table permissions and cloning |
| Date: | 2011-04-20 13:59:11 |
| Message-ID: | 25637.1303307951@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Shigeru Hanada <hanada(at)metrosystems(dot)co(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2011-04-20 14:00:12 | Re: pgbench \for or similar loop |
| Previous Message | Noah Misch | 2011-04-20 13:57:21 | Re: pg_dump --binary-upgrade vs. ALTER TYPE ... DROP ATTRIBUTE |