Re: Proposal: GRANT cascade to implicit sequences

From: Greg Stark <gsstark(at)mit(dot)edu>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Proposal: GRANT cascade to implicit sequences
Date: 2004-10-13 16:34:00
Message-ID: 87fz4i60hz.fsf@stark.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


Bruno Wolff III <bruno(at)wolff(dot)to> writes:

> I also think there is some merit in splitting the access rights for nextval
> and setval, so that insert access grants access to nextval and update access
> grants access to setval (or perhaps both nextval and setval). That way people
> who can just insert in the table can't set the sequence number backwards.

That might be a useful thing to do to sequences in general. Being able to
grant INSERT on a sequence to allow nextval without allowing setval could be
useful even for explicit sequences.

I can't think of a good approach for migration of old pg_dumps though, so
perhaps this is more trouble than it's worth.

Implicit sequences on the other hand can be migrated easily by ignoring all
explicit grants and just looking at the grants on the table.

--
greg

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Robin Ericsson 2004-10-13 16:36:26 Re: [PERFORM] query problem
Previous Message Robin Ericsson 2004-10-13 16:27:20 Re: [PERFORM] query problem