Re: [EXTERNAL] Re: Cannot connect local with ttrust (pg_upgrade assumes it) - Mailing list pgsql-general

From Abraham, Danny
Subject Re: [EXTERNAL] Re: Cannot connect local with ttrust (pg_upgrade assumes it)
Date
Msg-id cc2290e0-4fdd-465c-a282-efd5101d2f1b@bmc.com
Whole thread Raw
In response to Re: Cannot connect local with ttrust (pg_upgrade assumes it)  (Francisco Olarte <folarte@peoplecall.com>)
Responses Re: [EXTERNAL] Re: Cannot connect local with ttrust (pg_upgrade assumes it)
List pgsql-general
Failure eans going down the hba list and asking for the password.


Sent from Workspace ONE Boxer

On Apr 9, 2025 20:04, Francisco Olarte <folarte@peoplecall.com> wrote:
On Wed, 9 Apr 2025 at 18:20, Abraham, Danny <danny_abraham@bmc.com> wrote:
> Asking for help with inability to connect local using trust
> Fail
> #local   all         all                               trust
> #local   all   dbauser   peer
> OK
> #host    all          all         127.0.0.1/32          trust

How are you connecting? Your symptoms matches confusing local with
TCP/IP to localhost. They are not the same thing.
Also, are you on windows? ( which does not have unix sockets ).

local
This record matches connection attempts using Unix-domain sockets.
Without a record of this type, Unix-domain socket connections are
disallowed.
host
This record matches connection attempts made using TCP/IP. host
records match SSL or non-SSL connection attempts as well as GSSAPI
encrypted or non-GSSAPI encrypted connection attempts.

On a unix host psql -h localhost will use the host line, psql -h
/socket/path will go to the local one, and no -h defaults to socket.
On a windows host it default to tcp/ip to localhost.

Francisco Olarte.

pgsql-general by date:

Previous
From: "Abraham, Danny"
Date:
Subject: Re: [EXTERNAL] Re: Cannot connect local with ttrust (pg_upgrade assumes it)
Next
From: Adrian Klaver
Date:
Subject: Re: [EXTERNAL] Re: Cannot connect local with ttrust (pg_upgrade assumes it)