Re: pg_restore to a port where nobody is listening?

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Daniel Westermann <daniel(dot)westermann(at)dbi-services(dot)com>, pgsql-general(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: pg_restore to a port where nobody is listening?
Date: 2016-12-21 23:09:15
Message-ID: 54e6236f-eb86-b565-b0e6-bb0283588b48@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 12/21/2016 11:29 AM, Daniel Westermann wrote:

> Providing "-d" gives a meaningful message at least:
>
> postgres(at)pgbox:/home/postgres/ [PG961] pg_restore -h localhost -p
> ===6666 -d postgres -F d -C /var/tmp/exp/
> pg_restore: [archiver (db)] connection to database "postgres" failed:
> invalid port number: "===6666"
>
> Maybe it is only me, but this is not consistent behavior, is it?

Maybe so but that is why there is documentation for programs/commands ,
to deal with the exceptions. In this case the information is at the top
of the pg_restore docs. Generally whenever I get an odd result I head to
the bottom of the docs under the Notes section. This is usually where
the exceptions are called out.

>
>
> Regards
> Daniel

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2016-12-21 23:12:32 Re: pg_restore to a port where nobody is listening?
Previous Message Tom Lane 2016-12-21 22:58:45 Re: Disabling inheritance with query.