On Mon, Jun 23, 2008 at 11:03 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
>
> Frankly, there's going to be zero interest in any proposal to make this
> more flexible, because making it more flexible means opening a
> truck-sized security hole. We don't *want* Postgres loading code from
> random places
"P Kapat" <[EMAIL PROTECTED]> writes:
> 1. How should the admin go about adding $HOME/usr/local/lib to $PKGLIBDIR?
You don't. You can try editing the SQL CREATE FUNCTION commands as
I suggested before. If that doesn't work because of SELinux, you'll
need to get the admin to drop the shlibs into
Thanks Tom,
On Mon, Jun 23, 2008 at 7:53 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> "P Kapat" <[EMAIL PROTECTED]> writes:
>> If I understand correctly, the shared libraries for postgis should be
>> inside $PKGLIBDIR for the server to see them. Is there any userland
>> configuration (like adding $HO
"P Kapat" <[EMAIL PROTECTED]> writes:
> If I understand correctly, the shared libraries for postgis should be
> inside $PKGLIBDIR for the server to see them. Is there any userland
> configuration (like adding $HOME/usr/local/lib to ~/.psqlrc) that will
> solve this?
Do you have superuser privs on
Hi,
I am working on a RHEL 5 box where I do not have any administrative
access. But if need be, I can request the administrator to do some
changes. Currently the following packages are installed on the box:
postgresql.i386, postgresql-contrib.i386, postgresql-devel.i386,
postgresql-docs.i386, po
