Re: Re: Sure enough, the lock file is gone - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Re: Sure enough, the lock file is gone
Date
Msg-id 5855.980722390@sss.pgh.pa.us
Whole thread Raw
In response to Re: Re: Sure enough, the lock file is gone  (Lamar Owen <lamar.owen@wgcr.org>)
List pgsql-hackers
Lamar Owen <lamar.owen@wgcr.org> writes:
> I have another question of Peter, Tom, Bruce, or anyone -- is the
> hard-coded socket location in libpq?  If so, wouldn't a dynamically
> loaded libpq.so bring this location in for _any_ precompiled, not
> statically-linked, client?  Or am I missing something else?

As the 7.1 code presently stands, libpq contains a compiled-in default
socketfile location, which the client code hopefully doesn't know about.
So, yes, if an old client has a dynamically linked libpq.so then
replacing the .so would bring that client into sync with a nonstandard
server.  However, the pitfalls should be obvious: independently built
clients, statically linked libraries, differing .so version numbers
to name three risk areas.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Re: Sure enough, the lock file is gone
Next
From: Tom Lane
Date:
Subject: Re: Re: Sure enough, the lock file is gone