| From: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
|---|---|
| To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Cc: | Ewald Geschwinde <egeschwinde(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Nick Barr <nicky(at)chuckie(dot)co(dot)uk>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Truncate Permission |
| Date: | 2007-06-11 09:04:41 |
| Message-ID: | 466D1029.4070503@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Martijn van Oosterhout wrote:
> On Mon, Jun 11, 2007 at 09:40:08AM +0200, Ewald Geschwinde wrote:
>> My problem is that some users don't have access to change the structure but
>> they wanted to delete all data from the table
>> they try truncate - does not work because not the owner
>> so they make a delete from a really big table
>
> Wouldn't it be far more logical to decide that if a user has the
> permissions to do a DELETE FROM table; then they have permission to do
> a TRUNCATE? Why make an additional permission?
Truncate doesn't fire ON DELETE triggers.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2007-06-11 09:27:30 | Re: Controlling Load Distributed Checkpoints |
| Previous Message | Martijn van Oosterhout | 2007-06-11 08:59:05 | Re: Truncate Permission |