From: Tom Lane <tgl@sss.pgh.pa.us>
To: Scott Ribe <scott_ribe@elevated-dev.com>
Cc: Postgres Maillist <pgsql-admin@postgresql.org>
Subject: Re: unix socket location confusion
Date: Mon, 23 Mar 2015 00:54:11 -0400
Message-ID: <13189.1427086451@sss.pgh.pa.us> (raw)
In-Reply-To: <5600A100-C4A4-427D-938E-9FFDDBE87132@elevated-dev.com>
References: <0A21BC93-7B9C-476E-AAF4-0FF71708E87F@elevated-dev.com>
<3184.1427063304@sss.pgh.pa.us>
<3533.1427064190@sss.pgh.pa.us>
<5600A100-C4A4-427D-938E-9FFDDBE87132@elevated-dev.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
Scott Ribe <scott_ribe@elevated-dev.com> writes:
> On Mar 22, 2015, at 4:43 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> So this works only if your libpq.dylib is actually installed at the
>> location that was expected when you built it. The recipe you gave
>> looks like it should have done that, but I'm suspicious that the
>> answer is somewhere near here.
> Oh, take me out back and shoot me now ;-)
Uh huh :-(
> It's questionable whether the PG executables should be built with full or relative paths to the libs, both have their own disadvantages. But might be worth considering --relative-rpath someday? Or an option to link the frickin' static libraries in and avoid the whole issue of mismatches.
We're entirely at the mercy of the platform's dynamic loader when it comes
to things like this. I don't think I trust Darwin's loader with relative
paths; though come to think of it, Linux's loader may be no better. Way
too many opportunities to screw up there.
As for static libraries, there are good reasons why those aren't superior
solutions. Red Hat for instance has a blanket policy against shipping
static libraries (with only very narrow exceptions), and I believe the
same is true of many other vendors.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, scott_ribe@elevated-dev.com
Subject: Re: unix socket location confusion
In-Reply-To: <13189.1427086451@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox