Skip site navigation (1) Skip section navigation (2)

Re: problem in restoring database when connected via named socket

From: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
To: Giuseppe Sacco <giuseppe(at)eppesuigoccas(dot)homedns(dot)org>
Cc: pgadmin-support(at)postgresql(dot)org
Subject: Re: problem in restoring database when connected via named socket
Date: 2010-01-12 10:21:32
Message-ID: 4B4C4D2C.4030607@lelarge.info (view raw or flat)
Thread:
Lists: 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.org
 http://dalibo.com

In response to

Responses

pgadmin-support by date

Next:From: Giuseppe SaccoDate: 2010-01-12 10:51:25
Subject: Re: problem in restoring database when connected via named socket
Previous:From: Giuseppe SaccoDate: 2010-01-12 10:08:43
Subject: Re: problem in restoring database when connected via named socket

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group