Re: Only owners can ANALYZE tables...seems overly restrictive

Поиск
Список
Период
Сортировка
От Stephen Frost
Тема Re: Only owners can ANALYZE tables...seems overly restrictive
Дата
Msg-id 20160229133138.GV3127@tamriel.snowman.net
обсуждение исходный текст
Ответ на Only owners can ANALYZE tables...seems overly restrictive  ("David G. Johnston" <david.g.johnston@gmail.com>)
Ответы Re: Only owners can ANALYZE tables...seems overly restrictive  (Guillaume Lelarge <guillaume@lelarge.info>)
Re: Only owners can ANALYZE tables...seems overly restrictive  ("David G. Johnston" <david.g.johnston@gmail.com>)
Re: Only owners can ANALYZE tables...seems overly restrictive  ("Joshua D. Drake" <jd@commandprompt.com>)
Список pgsql-general
* David G. Johnston (david.g.johnston@gmail.com) wrote:
> Given the amount of damage a person with write access to a table can get
> into it seems pointless to not allow them to analyze the table after their
> updates - since best practices would say that normal work with a table
> should not be performed by an owner.
>
> I should the check for whether a given user can or cannot analyze a table
> should be whether the user has INSERT, UPDATE, or DELETE privileges.

Realistically, ANALYZE is a background/maintenance task that autovacuum
should be handling for you.

> I suppose row-level-security might come into play here...

Yes, you may only have access to a subset of the table.

If we had plenty more bits to allow ANALYZE to be independently
GRANT'able, then maybe, but those are a limited resource.

Thanks!

Stephen

Вложения

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

Предыдущее
От: Rafal Pietrak
Дата:
Сообщение: Re: multiple UNIQUE indices for FK
Следующее
От: Geoff Winkless
Дата:
Сообщение: multicolumn index and setting effective_cache_size using human-readable-numbers