Tom Lane wrote:
>>It seems like you could handle all the above with just a shell script wrapper.
>> All three, the library path, socket directory, and data directory can be
>>specified either in environment or on the command line. Where are you getting
>>stuck?
>
> No, we only handle two of the three; library directory is currently
> hard-coded into the server. At the moment that's seeming like a
> mistake. I wonder why it's not a GUC variable (probably postmaster-only
> for security). Peter, do you recall why you didn't migrate that setting
> into GUC?
Yes, $libdir is hardcoded, which is why in my case I'm not using
'$libdir/plruby.so' but using just 'plruby.so' (no absolute path) so
Postgres can look it up with dynamic_library_path. Will this be unsafe?
--
dave