"Keith Worthington" <keithw(at)narrowpathinc(dot)com> writes:
> On Thu, 24 Feb 2005 17:15:42 -0500, Tom Lane wrote
>> Yeah. I've dropped the idea personally -- the suggestion that the table
>> owner can provide a SECURITY DEFINER procedure to do the TRUNCATE if
>> he wants to allow others to do it seems to me to cover the problem.
> Could someone point me in the direction of documentation on this SECURITY
> DEFINER feature?
See CREATE FUNCTION. Something like (untested)
create function truncate_my_table() returns void as
$$ truncate my_table $$ language sql security definer;
You'd probably then revoke the default public EXECUTE rights on this
function, and grant EXECUTE only to selected users.
regards, tom lane
In response to
pgsql-novice by date
|Next:||From: Ross Gohlke||Date: 2005-02-25 01:03:50|
|Subject: Using upper() / decode() together|
|Previous:||From: Keith Worthington||Date: 2005-02-24 22:28:08|
|Subject: Re: [NOVICE] Question on TRUNCATE privleges |
pgsql-hackers by date
|Next:||From: Eric Crampton||Date: 2005-02-24 22:49:00|
|Subject: Patch for Postmaster Uptime (from the TODO)|
|Previous:||From: Marc G. Fournier||Date: 2005-02-24 22:40:37|
|Subject: Re: Some download statistics |