Re: security_definer_search_path GUC
| От | Pavel Stehule |
|---|---|
| Тема | Re: security_definer_search_path GUC |
| Дата | |
| Msg-id | CAFj8pRCzzmWdRivSK88eNe2fsx-HHChuz_v96bax=uje+vnM0Q@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: security_definer_search_path GUC ("Joel Jacobson" <joel@compiler.org>) |
| Ответы |
Re: security_definer_search_path GUC
|
| Список | pgsql-hackers |
Hi
I realise "eliminate" is not really necessary, it would suffice to just allow setting a a sane default per database, and make that value immutable, then all data structures and code using wouldn't need to change, one would then only need to change the code that can mutate search_path, to prevent that from happening.
I understand that for some specific cases the search_path can be problematic. On the other hand, the SQL database supports interactive work, and then the search_path can save a lot of monkey work.
It is the same as using the command line without the possibility to customize the PATH variable. The advantages and disadvantages are exactly the same.
Regards
Pavel
В списке pgsql-hackers по дате отправления: