pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Aasmund Midttun Godal <postgresql@envisity.com>
To: tgl@sss.pgh.pa.us
Cc: pgsql-sql@postgresql.org
Subject: Re: Sequence permission suggestion
Date: Mon, 26 Nov 2001 05:52:20 GMT
Message-ID: <20011126055220.25507.qmail@ns.krot.org> (raw)
In-Reply-To: <7249.1006737562@sss.pgh.pa.us>
References: <20011126005514.10436.qmail@ns.krot.org>
	<7249.1006737562@sss.pgh.pa.us>

I cannot argue this on a philosophical level, because I have no idea what the SQL92 papers say or don't say, and all the database books I have read generally talk very little about permissions. However allowing someone to nextval and allowing setval is to radically different things - perhaps comparable to inserting or updating a table, even though both, technically, are updates. 

There are many ways to attack this issue one could have different set of permission names on a sequence than on tables and views etc. A functional and practical approach would be to do as you suggested. I would be very interested to know what philosophy there is about security in postgres in general - I have looked around on the lists but I can't find much discussion on this (except the TODO.privileges) - personally I find it an integral part of a database solution - what can be done and who can do it. If anyone can shed any light on this issue, I would greatly appreciate it!

Regards,

Aasmund




On Sun, 25 Nov 2001 20:19:22 -0500, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> "Aasmund Midttun Godal" <postgresql@envisity.com> writes:
> 
> 
> It looks like an update to me; in particular, it allows you to determine
> the old state of the sequence, and thus has read+write semantics not
> only write semantics.
> 
> 
> This seems to be exceedingly SERIAL-centric thinking; there are other
> uses for sequences than serials.
> 
> It might make sense to allow either INSERT or UPDATE permission to
> grant nextval() access, while still requiring UPDATE for setval().
> But I'm not convinced yet ...
> 
> 			regards, tom lane
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)

Aasmund Midttun Godal

aasmund@godal.com - http://www.godal.com/
+47 40 45 20 46



view thread (3+ messages)

Message-ID: <20011126055220.25507.qmail@ns.krot.org>
Permalink:  ../20011126055220.25507.qmail@ns.krot.org/
Also on:    postgresql.org/message-id/20011126055220.25507.qmail@ns.krot.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: postgresql@envisity.com, tgl@sss.pgh.pa.us
  Subject: Re: Sequence permission suggestion
  In-Reply-To: <20011126055220.25507.qmail@ns.krot.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox