Re: Printing backtrace of postgres processes
От | Tom Lane |
---|---|
Тема | Re: Printing backtrace of postgres processes |
Дата | |
Msg-id | 4174276.1620327369@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Printing backtrace of postgres processes (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: Printing backtrace of postgres processes
|
Список | pgsql-hackers |
Robert Haas <robertmhaas@gmail.com> writes: > On Wed, Feb 3, 2021 at 2:30 AM Tom Lane <tgl@sss.pgh.pa.us> wrote: >> TBH, I'm leaning to the position that this should be superuser >> only. > I agree that ordinary users shouldn't be able to trigger it, but I > think it should be restricted to some predefined role, new or > existing, rather than to superuser. I see no reason not to let > individual users decide what risks they want to take. If we think it's worth having a predefined role for, OK. However, I don't like the future I see us heading towards where there are hundreds of random predefined roles. Is there an existing role that it'd be reasonable to attach this ability to? regards, tom lane
В списке pgsql-hackers по дате отправления: