Re: [HACKERS] RFC: Industrial-strength logging
От | Aaron J. Seigo |
---|---|
Тема | Re: [HACKERS] RFC: Industrial-strength logging |
Дата | |
Msg-id | 99102515535807.00882@stilborne обсуждение исходный текст |
Ответ на | Re: [HACKERS] RFC: Industrial-strength logging (Peter Eisentraut <peter_e@gmx.net>) |
Ответы |
Re: [HACKERS] RFC: Industrial-strength logging
|
Список | pgsql-hackers |
hi... > What about > SET LOGLEVEL TO <something>; > SET LOGDETAIL TO <something>; > or the like. You could use pg_shadow.usesuper as a security stipulation. > Using something like a signal to do this is probably overkill, especially > since there are hardly any left, and it's also infinitely less intuitive > and flexible. this would be done from psql? if so, here's a query i have: are there any plans to seperate the admin functions out of psql and into another seperate tool? i have a queasyness with general users having access to a tool that can do admin takss (even if they supposedly don't have a superuser account). it also seems much cleaner to have admin in one tool and data interaction in another. am i off track here? -- Aaron J. Seigo Sys Admin
В списке pgsql-hackers по дате отправления: