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

From Tom Lane
Subject Re: Foreign table permissions and cloning
Date
Msg-id 18033.1303756269@sss.pgh.pa.us
Whole thread Raw
In response to Re: Foreign table permissions and cloning  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Foreign table permissions and cloning  (Robert Haas <robertmhaas@gmail.com>)
List 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


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: "stored procedures"
Next
From: Merlin Moncure
Date:
Subject: Re: "stored procedures"