Tom Lane wrote:
> Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
>> That way you could
>> grant SELECT_FOR_SHARE permission on a table to let people insert rows
>> into other tables that have a foreign key reference to it, without
>> having to grant UPDATE permission.
>
> ... but this argument for it is utter nonsense. FKs are not a
> permissions problem, because the triggers run as the table's owner.
> The only permission you need is REFERENCES:
Then I think we should leave it as it is. I don't see any plausible use
case for a separate SELECT FOR SHARE or UPDATE permission.
-- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com