Re: A modest proposal: get rid of GUC's USERLIMIT variable category
От | Greg Stark |
---|---|
Тема | Re: A modest proposal: get rid of GUC's USERLIMIT variable category |
Дата | |
Msg-id | 87mzxqgu0x.fsf@stark.xeocode.com обсуждение исходный текст |
Ответ на | A modest proposal: get rid of GUC's USERLIMIT variable category (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: A modest proposal: get rid of GUC's USERLIMIT variable
Re: A modest proposal: get rid of GUC's USERLIMIT variable Re: A modest proposal: get rid of GUC's USERLIMIT variable category |
Список | pgsql-hackers |
Tom Lane <tgl@sss.pgh.pa.us> writes: > I'd like to propose that we get rid of GUC's USERLIMIT category and > convert all the variables in it to plain SUSET. In my mind, USERLIMIT > is a failed experiment: it's way too complicated, and it still doesn't > do quite what it was intended to do, because there are times when it > can't check whether you're a superuser. > > The only variables that are in the category are log-verbosity-related: Would that mean I wouldn't be able to change the logging level on the fly at all? That would disappoint at least one user, myself. I've found the best debugging compromise is to leave log_statement off in general but have a magic parameter I can pass to the application that will set log_statement = true for a single transaction. That way I can look at what queries transpired in my session without having to dig through hundreds of other queries from other sessions. And have the complete logs for the session I'm debugging without the performance impact in the normal case. -- greg
В списке pgsql-hackers по дате отправления: