From: Tom Lane <tgl@sss.pgh.pa.us>
To: Brian Powell <brian@owlscreech.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Permissions Broken in 7.0.x?
Date: Tue, 21 Nov 2000 16:14:18 -0500
Message-ID: <2953.974841258@sss.pgh.pa.us> (raw)
In-Reply-To: <B640265D.1448%brian@owlscreech.com>
References: <B640265D.1448%brian@owlscreech.com>
Brian Powell <brian@owlscreech.com> writes:
> % psql bobdb
> psql => create table test (
> name char(32) not null,
> age int4
> );
> psql => revoke all on test from tester;
> CHANGE
> psql => select * from test;
> ERROR: test: Permission denied.
Yeah, that's a bug --- confusion about the default permissions set.
After doing an explicit GRANT or REVOKE on a table you own, you need to
grant permissions to yourself again; the default assumption that you
have all permissions gets lost :-(. This is fixed for 7.1.
> Additionally, if I have a trigger on a table which sets the updated_date and
> updated_by on any update, and I have a view with a rule which passes any
> update to the table (thus calling the trigger), I get a permission denied.
> I am supposing that the user updating the view does not have privileges to
> the trigger? How would I grant them privileges to the trigger?
Don't think there's a way to do that right now. There's been talk of
making triggers run "setuid" to the creating user, but it's not been
done AFAIR.
regards, tom lane
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, brian@owlscreech.com
Subject: Re: Permissions Broken in 7.0.x?
In-Reply-To: <2953.974841258@sss.pgh.pa.us>
References: <B640265D.1448%brian@owlscreech.com> <2953.974841258@sss.pgh.pa.us>
* 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