Re: Dynamic loading of C functions: Badly stuck

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Jasbinder Bali" <jsbali(at)gmail(dot)com>
Cc: "Joe Conway" <mail(at)joeconway(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Dynamic loading of C functions: Badly stuck
Date: 2006-06-21 19:29:30
Message-ID: 15529.1150918170@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Jasbinder Bali" <jsbali(at)gmail(dot)com> writes:
> I've disabled my SELinux and now postgres is being able to access the shared
> library i.e test.so file.
> Don't know if thats the right way to do it or not.

It's not. Almost certainly, SELinux is keying the rejection off the
fact that you have the .so file in the wrong place, ie, not a place that
postgres is supposed to be reading executables from.

Put it in $libdir and everything will be much better. (You might also
need to run restorecon on it, not sure.) "pg_config --pkglibdir" will
tell you where that is.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Hrishikesh Deshmukh 2006-06-21 19:41:54 MS-SQL2PostgreSQL
Previous Message Jasbinder Bali 2006-06-21 18:44:38 Re: Dynamic loading of C functions: Badly stuck