Re: Truncate Permission

Поиск
Список
Период
Сортировка
От Ewald Geschwinde
Тема Re: Truncate Permission
Дата
Msg-id cf42ed390706110040h39f641ebs5da395699bd3f18f@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Truncate Permission  (Stephen Frost <sfrost@snowman.net>)
Ответы Re: Truncate Permission  (Martijn van Oosterhout <kleptog@svana.org>)
Список pgsql-hackers

Yes, there is a use-case for it.  If you don't have triggers or
transactional concerns on the table and you want users to be able to
truncate tables while not allowing them to do things like change the
table structure.  I proposed a patch a while ago to implement a seperate
permission for truncate but it was turned down because of concern over
using the few remaining bits in the ACL structure.



I second this proposal
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

So I would like to see a truncate permission - makes some things easier in my opinion
--
Ewald Geschwinde
http://www.postgresql.at

В списке pgsql-hackers по дате отправления:

Предыдущее
От: ITAGAKI Takahiro
Дата:
Сообщение: Re: Controlling Load Distributed Checkpoints
Следующее
От: Kris Jurka
Дата:
Сообщение: Re: So, why isn't *every* buildfarm member failing ecpg right now?