Re: psql thinks we should be listening on port 5432 - Mailing list pgsql-novice

From Day, David
Subject Re: psql thinks we should be listening on port 5432
Date
Msg-id 401084E5E73F4241A44F3C9E6FD7942828755A59@exch-01
Whole thread Raw
In response to psql thinks we should be listening on port 5432  ("Struckhoff, Kevin" <StruckhoffK@gsicommerce.com>)
List pgsql-novice

Hi

 

I suggest you start psql with the port declaration switch –p 8432,

By default it is using 5432

 

Rgds

 

 

Dave

 

From: pgsql-novice-owner@postgresql.org [mailto:pgsql-novice-owner@postgresql.org] On Behalf Of Struckhoff, Kevin
Sent: Tuesday, February 21, 2012 7:00 PM
To: pgsql-novice@postgresql.org
Subject: [NOVICE] psql thinks we should be listening on port 5432

 

Hello,

 

I’m running postgres 8.4.5, it was bundled w/ Actuate 11 Iserver. It was configured to run on port 8432 (not sure why or if that can be changed, I suspect it doesn’t matter in the long run). When I try to run psql, I get this error:

 

/usr/local/actuate11/AcServer/postgresql/bin->psql -d ac_dr_reports

psql: could not connect to server: No such file or directory

        Is the server running locally and accepting

        connections on Unix domain socket "/tmp/.s.PGSQL.5432"?

/usr/local/actuate11/AcServer/postgresql/bin->

 

How do I tell it to look on port 8432?

 

Here’s the files in /tmp:

 

srwxrwxrwx  1 actuate actuate     0 Feb 21 15:23 .s.PGSQL.8432

-rw-------  1 actuate actuate    62 Feb 21 15:23 .s.PGSQL.8432.lock

 

 

Thanks.

 

Kevin

 

pgsql-novice by date:

Previous
From: Tom Lane
Date:
Subject: Re: Export Control Classification Number (ECCN) Request
Next
From: Ganesh Borse
Date:
Subject: Re: select on bytea column returns hex encoded data instead of binary data