From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Alastair D'Silva" <deece(at)newmillennium(dot)net(dot)au> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: PostgreSQL 7.1 and Sequences |
Date: | 2001-04-22 16:08:02 |
Message-ID: | 27858.987955682@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Alastair D'Silva" <deece(at)newmillennium(dot)net(dot)au> writes:
> I've recently upgraded to 7.1 and have the following situation which no
> longer works:
> As user "nmnadmin":
> CREATE TABLE blah {
> id NOT NULL SERIAL,
> info text NOT NULL
> };
> GRANT SELECT, INSERT, UPDATE, DELETE ON blah TO nmnuser;
> As user "nmnuser":
> INSERT INTO blah (info) VALUES ('foo');
> I get the following error:
> blah_id_seq.nextval: you don't have permissions to set sequence blah_id_seq
You should also do
GRANT UPDATE ON blah_id_seq TO nmnuser;
I am not sure whether to regard the change from 7.0 behavior as a bug or
not. The old handling of permission-checking for sequences was pretty
broken, and I don't want to revert to it.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alex Pilosov | 2001-04-22 16:08:22 | Re: last comma inside "CREATE TABLE ()" statements |
Previous Message | Thomas Lockhart | 2001-04-22 16:04:36 | Re: Hardcopy docs available |