On Thu, Jun 7, 2012 at 11:57 AM, Andres Freund <andres@2ndquadrant.com> wrote:
> On Thursday, June 07, 2012 05:55:11 PM Tom Lane wrote:
>> Honza Horak <hhorak@redhat.com> writes:
>> > On 06/06/2012 04:50 PM, Andres Freund wrote:
>> >> I wonder if the whole issue doesn't require libpq to also try multiple
>> >> hardcoded socket locations.
>> >
>> > I guess so.
>>
>> I don't really want to go there. Some use cases have been shown in
>> this thread for having a server listen in multiple places, but that does
>> not translate to saying that clients need to support automatically
>> looking in multiple places. I think that mainly introduces questions we
>> could do without, like which server did you actually end up contacting.
> It would be really nice to have a development psql connect to a distro
> installed psql and vice versa without having to specify -h /var/run/psql and -
> h /tmp all the time...
This is true, but you have this problem already. It might be worth
fixing, but it seems like a separate issue from the topic of this
thread, which is where the server listens.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company