Re: problem in restoring database when connected via named socket - Mailing list pgadmin-support

From Guillaume Lelarge
Subject Re: problem in restoring database when connected via named socket
Date
Msg-id 4B4C4D2C.4030607@lelarge.info
Whole thread Raw
In response to Re: problem in restoring database when connected via named socket  (Giuseppe Sacco <giuseppe@eppesuigoccas.homedns.org>)
Responses Re: problem in restoring database when connected via named socket  (Giuseppe Sacco <giuseppe@eppesuigoccas.homedns.org>)
List pgadmin-support
Le 12/01/2010 11:08, Giuseppe Sacco a écrit :
> Hi Guillaume,
> 
> Il giorno mar, 12/01/2010 alle 10.47 +0100, Guillaume Lelarge ha
> scritto:
>> Hi Giuseppe,
> [...]
>> You shouldn't have this issue because we check if the server name is
>> empty or not before adding the -h command line option. AFAICT, this is
>> fixed since "Wed Mar 19 11:28:37 2008". So I assume you have a rather
>> old release. Try on a current one (current being 1.10.1 right now).
> 
> Right, I am using 1.9. Yesterday I tried to update source from
> repository, but I did not manage to compile it because of a link error.
> I'll try again later on.
> 

Did you re-run ./bootstrap? if not, try to do so.


-- 
Guillaume.http://www.postgresqlfr.orghttp://dalibo.com


pgadmin-support by date:

Previous
From: Giuseppe Sacco
Date:
Subject: Re: problem in restoring database when connected via named socket
Next
From: Giuseppe Sacco
Date:
Subject: Re: problem in restoring database when connected via named socket