Re: Controlling access to Sequences - Mailing list pgsql-sql

From Tom Lane
Subject Re: Controlling access to Sequences
Date
Msg-id 4109.1044072571@sss.pgh.pa.us
Whole thread Raw
In response to Controlling access to Sequences  (Matthew Horoschun <mhoroschun@canprint.com.au>)
Responses Re: Controlling access to Sequences  (Matthew Horoschun <mhoroschun@canprint.com.au>)
List pgsql-sql
Matthew Horoschun <mhoroschun@canprint.com.au> writes:
> My understanding is that I need to GRANT the UPDATE privilege on the 
> SEQUENCE if I want a user to be able to to use nextval() on it. The 
> trouble is, if they can do a nextval() they can also do a setval() 

So?  With enough time on your hands, you can apply nextval() often
enough to get from any point A to any point B.  It seems illusory
to think that forbidding setval() makes things more secure.
        regards, tom lane


pgsql-sql by date:

Previous
From: Matthew Horoschun
Date:
Subject: Controlling access to Sequences
Next
From: Matthew Horoschun
Date:
Subject: Re: Controlling access to Sequences