Re: unix socket location confusion - Mailing list pgsql-admin

From Scott Ribe
Subject Re: unix socket location confusion
Date
Msg-id 0CA66AE2-6929-41A0-B735-C5B510650486@elevated-dev.com
Whole thread Raw
In response to Re: unix socket location confusion  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin
On Mar 22, 2015, at 10:54 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> 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.

It actually does work, I've used it. But I never found any documentation about it, and it was a damned PITA to figure
out.

> 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.

Yep. Good & bad both ways.

Anyway, I clearly need to not nest specific version builds with the dbs that use that version. I need to build all
versionsinto /usr/local/pgsql-XYZ and then symlink as needed. 

--
Scott Ribe
scott_ribe@elevated-dev.com
http://www.elevated-dev.com/
https://www.linkedin.com/in/scottribe/
(303) 722-0567 voice







pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: unix socket location confusion
Next
From: Alexey Klyukin
Date:
Subject: Re: pg_ugprade and missing timeline