Skip site navigation (1) Skip section navigation (2)

Re: Permissions vs SERIAL columns

From: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
To: Magnus Hagander <mha(at)sollentuna(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Permissions vs SERIAL columns
Date: 2006-01-03 16:07:12
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
If nothing else, this should at least be documented in

On Fri, Dec 30, 2005 at 07:32:18PM +0100, Magnus Hagander wrote:
> Haven't seen this discussed in a while, but I do recall it being
> mentioned sometime before...
> The problem:
> testdb=# create table mytable (id serial, txt text);
> testdb=# grant insert on mytable to user2;
> testdb=# \connect testdb user2
> You are now connected to database "testdb" as user "user2".
> testdb=> insert into mytable (txt) values ('foobar');
> ERROR:  permission denied for sequence mytable_id_seq
> What I'd like to happen is for the grant for INSERT on the table to
> cascade into an UPDATE permission on the sequence (when associated with
> a SERIAL column only, of course).
> Coming from a different database, such as MSSQL, makes people forget
> this very easily, and it becomes very annoying.
> Is this something that can be done without too much work? Anything you
> can do in current pg even, just me not knowing how?
> //Magnus
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
>        subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
>        message can get through to the mailing list cleanly

Jim C. Nasby, Sr. Engineering Consultant      jnasby(at)pervasive(dot)com
Pervasive Software    work: 512-231-6117
vcard:       cell: 512-569-9461

In response to


pgsql-hackers by date

Next:From: Jim C. NasbyDate: 2006-01-03 16:18:12
Subject: Re: Why don't we allow DNS names in pg_hba.conf?
Previous:From: Jim C. NasbyDate: 2006-01-03 15:58:34
Subject: Re: [Bizgres-general] WAL bypass for INSERT, UPDATE and

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group