Re: predefined role(s) for VACUUM and ANALYZE

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: predefined role(s) for VACUUM and ANALYZE
Дата
Msg-id CA+Tgmoa5A4+OVCm5Uiwgd2=M=zNT6nSxA2xh_60=UY5xKttJsA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: predefined role(s) for VACUUM and ANALYZE  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Ответы Re: predefined role(s) for VACUUM and ANALYZE  ("David G. Johnston" <david.g.johnston@gmail.com>)
Список pgsql-hackers
On Mon, Jul 25, 2022 at 9:47 PM Kyotaro Horiguchi
<horikyota.ntt@gmail.com> wrote:
> One arguable point would be whether we will need to put restriction
> the target relations that Bob can vacuum/analyze.

Yeah. pg_checkpoint makes sense because you can either CHECKPOINT or
you can't. But for a command with a target, you really ought to have a
permission on the object, not just a general permission. On the other
hand, we do have things like pg_read_all_tables, so we could have
pg_vacuum_all_tables too. Still, it seems somewhat appealing to give
people fine-grained control over this, rather than just "on" or "off".

-- 
Robert Haas
EDB: http://www.enterprisedb.com



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

Предыдущее
От: Nathan Bossart
Дата:
Сообщение: out of date comment in commit_ts.c
Следующее
От: Andres Freund
Дата:
Сообщение: Re: failures in t/031_recovery_conflict.pl on CI