Re: extension_control_path
| От | Greg Stark |
|---|---|
| Тема | Re: extension_control_path |
| Дата | |
| Msg-id | CAM-w4HPorv3rU8B+iOJ_F0AMOn0oV_NH45RG+7YHJFMdEiehbQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: extension_control_path ("David E. Wheeler" <david@justatheory.com>) |
| Ответы |
Re: extension_control_path
Re: extension_control_path |
| Список | pgsql-hackers |
On Tue, Feb 4, 2014 at 6:07 PM, David E. Wheeler <david@justatheory.com> wrote: > The install failed, of course, because extensions want to install in $PGROOT/share/extensions. Homebrew sounds kind of confused. Having a non-root user have access to make global system changes sounds like privilege escalation vulnerability by design. However putting that aside, it is fairly standard for software to provide two directories for extensions/modules/plugins/etc. One for distribution-built software such as /usr/share/emacs/site-lisp/ and another for sysadmin customizations such as /usr/local/share/emacs/site-lisp. The same idea as /usr/share/perl and /usr/local/share/perl or with Python or anything else. -- greg
В списке pgsql-hackers по дате отправления: