Re: [EXTERNAL] Re: Cannot connect local with ttrust (pg_upgrade assumes it)

On 4/9/25 10:45 AM, Abraham, Danny wrote:
> Failure eans going down the hba list and asking for the password.

In pg_hba.conf first match wins, sounds like you have password auth line
before the trust lines.

You need to provide the complete pg_hba.conf auth lines you are working
with.

>
>
> Sent from Workspace ONE Boxer
>
> On Apr 9, 2025 20:04, Francisco Olarte <folarte(at)peoplecall(dot)com> wrote:
> On Wed, 9 Apr 2025 at 18:20, Abraham, Danny <danny_abraham(at)bmc(dot)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.

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