Thanks a lot. As you mentioned , I have not cleared the environment vars prior to the call.
==> dba-tlv-x6y64k% cat d2 unsetenv PGPORT unsetenv PGSYSCONFDIR unsetenv PGUSER unsetenv PGDATABASE unsetenv PGSERVICE unsetenv PGHOST psql -Upostgres -p5548 -dpostgres dba-tlv-x6y64k% source d2 psql (17.4) Type "help" for help. postgres=# \q ==> -----Original Message----- From: Adrian Klaver <adrian.kla...@aklaver.com> Sent: Thursday, April 10, 2025 12:00 AM To: Abraham, Danny <danny_abra...@bmc.com>; David G. Johnston <david.g.johns...@gmail.com>; Francisco Olarte <fola...@peoplecall.com>; pgsql-general@lists.postgresql.org Subject: Re: [EXTERNAL] Re: Cannot connect local with ttrust (pg_upgrade assumes it) On 4/9/25 13:40, Abraham, Danny wrote: > Thanks again. > 4. I am not aware of an env variable that changes the top down matching > on pg_hba.conf Should have added to previous post: From here: https://urldefense.com/v3/__https://www.postgresql.org/docs/current/runtime-config-logging.html*RUNTIME-CONFIG-LOGGING-WHAT__;Iw!!PEZBYkTc!fcUdccPVwqMg5ysFSTgyVxuCPBLFdOMxwtMMj5-n6H2aJ4D-3IzJZsdkw3lk43mUrVgdNhgWhX0O-ZGdU-6PAaXcmFI$ a) Set log_connections and log_disconnections to on if they are not already and reload the server conf. b) Then look at Postgres log to see what the connection settings are for the connections in question. > > Danny > -- Adrian Klaver adrian.kla...@aklaver.com
