Re: Foreign table permissions and cloning
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Shigeru Hanada <hanada@metrosystems.co.jp>, Thom Brown <thom@linux.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2011-04-25T18:31:09Z
Lists: pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes: > ... There's a similar stanza for sequences, but that one uses > ereport(WARNING...) rather than ereport(ERROR...). We could either > remove that stanza entirely (making foreign tables consistent with > views) or change ERROR to WARNING (making it consistent with > sequences). Well, the relevant point here is that there's little or no likelihood that we'll ever care to support direct UPDATE on sequences. This is exactly not the case for foreign tables. So I would argue that GRANT should handle them like views; certainly not be even more strict than it is for sequences. IOW, yeah, let's drop these two checks. regards, tom lane