Re: extension_control_path - Mailing list pgsql-hackers

From Greg Stark
Subject Re: extension_control_path
Date
Msg-id CAM-w4HPorv3rU8B+iOJ_F0AMOn0oV_NH45RG+7YHJFMdEiehbQ@mail.gmail.com
Whole thread Raw
In response to Re: extension_control_path  ("David E. Wheeler" <david@justatheory.com>)
Responses Re: extension_control_path
Re: extension_control_path
List 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 by date:

Previous
From: Rafael Martinez Guerrero
Date:
Subject: open and close columns in the NEW record not allowed
Next
From: Alvaro Herrera
Date:
Subject: Re: updated emacs configuration