Il giorno mar, 12/01/2010 alle 11.21 +0100, Guillaume Lelarge ha
scritto:
> Did you re-run ./bootstrap? if not, try to do so.
I didn't. That fixed the problem.
Thanks again,
Giuseppe
--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to your subscription
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. AF
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
Hi all,
I am connected to a local postgresql server via named pipe instead of
tcp/ip socket, i.e., I did not specify the hostname while creating the
connection.
No, when I try to restore a database, the command fail since the
"hostname" argument is missing. This is the error message I get:
/usr/b
Hi Giuseppe,
Le 12/01/2010 10:34, Giuseppe Sacco a écrit :
> [...]
> I am connected to a local postgresql server via named pipe instead of
> tcp/ip socket, i.e., I did not specify the hostname while creating the
> connection.
>
> No, when I try to restore a database, the command fail since the
>
Hi all,
I am connected to a local postgresql server via named pipe instead of
tcp/ip socket, i.e., I did not specify the hostname while creating the
connection.
No, when I try to restore a database, the command fail since the
"hostname" argument is missing. This is the error message I get:
/usr/b
