Re: BUG #16086: Cannot connect using psql, however I can connect using pgadmin

From: Euler Taveira <euler(at)timbira(dot)com(dot)br>
To: Muziwandile Zwane <mzwai99(at)outlook(dot)com>
Cc: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, PG Bug reporting form <noreply(at)postgresql(dot)org>, pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #16086: Cannot connect using psql, however I can connect using pgadmin
Date: 2019-10-29 23:56:26
Message-ID: CAHE3wgjkn4Desdca-nm45M4U6cPSs24jfSxmF6BrFHavvOTkzA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Em ter, 29 de out de 2019 às 08:54, Muziwandile Zwane
<mzwai99(at)outlook(dot)com> escreveu:
>
> I wanted to change the port from default to 5437, initially it worked, but suddendly I had issues connecting.
> I changed the port postgresql.conf back to 5432.
>
... if you change the port, you should specify it in psql command-line.

> [root(at)zardplpsmasdev01 data]# su - postgres -c "psql"
> psql (12.0)
> Type "help" for help.
>
su - postgres -c "psql -p 5437"

The default port (5432 or what it was compiled with) is hardcoded in
all postgres binaries. If you change the port to something else, you
should specify --port (-p) parameter or set PGPORT variable.

--
Euler Taveira Timbira -
http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Pavel Popov 2019-10-30 08:15:18 Re: Backup/restore problem
Previous Message Tom Lane 2019-10-29 15:37:05 Re: BUG #16088: Multiple foreigh keys created on "ALTER TABLE" command