Re: Cannot connect local with ttrust (pg_upgrade assumes it)
От | Francisco Olarte |
---|---|
Тема | Re: Cannot connect local with ttrust (pg_upgrade assumes it) |
Дата | |
Msg-id | CA+bJJby+nA8OVs7AZKgGBX2Dx3ApvhEceWtFiq97crkiER2A=Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Cannot connect local with ttrust (pg_upgrade assumes it) ("Abraham, Danny" <danny_abraham@bmc.com>) |
Ответы |
Re: [EXTERNAL] Re: Cannot connect local with ttrust (pg_upgrade assumes it)
Re: [EXTERNAL] Re: Cannot connect local with ttrust (pg_upgrade assumes it) |
Список | pgsql-general |
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 по дате отправления: