| From: | Francisco Olarte <folarte(at)peoplecall(dot)com> |
|---|---|
| To: | "Abraham, Danny" <danny_abraham(at)bmc(dot)com> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [EXTERNAL] Re: Cannot connect local with ttrust (pg_upgrade assumes it) |
| Date: | 2025-04-10 11:36:49 |
| Message-ID: | CA+bJJbxFFYXQE+LXhes0=7O9USmxb+3SJZVoq7f+HXPPr_o9ug@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Abraham:
On Thu, 10 Apr 2025 at 13:30, Francisco Olarte <folarte(at)peoplecall(dot)com> wrote:
> You forgot to answer the first and most important question.
> > How are you connecting? Your symptoms matches confusing local with
> > TCP/IP to localhost. They are not the same thing.
After reading more messages it seems you use plain psql -U.
Can you try to do \conninfo after connecting to see how you are connecting?
- If it says tcp, then it is a problem with how psql determines where
to connect.
- If it says local then it may be an hba problem.
Francisco Olarte.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitrios Apostolou | 2025-04-10 12:11:57 | Re: pg_restore causing ENOSPACE on the WAL partition |
| Previous Message | Francisco Olarte | 2025-04-10 11:30:27 | Re: [EXTERNAL] Re: Cannot connect local with ttrust (pg_upgrade assumes it) |