Thanks again.
1. No other PG instances on this Linux machine. 2. RHEL9 3. Our compiled PG which is embedded within our product/site 4. I am not aware of an env variable that changes the top down matching on pg_hba.conf Danny From: David G. Johnston <david.g.johns...@gmail.com> Sent: Wednesday, April 9, 2025 10:34 PM To: Abraham, Danny <danny_abra...@bmc.com> Cc: Adrian Klaver <adrian.kla...@aklaver.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 Wed, Apr 9, 2025, 12:21 Abraham, Danny <danny_abra...@bmc.com<mailto:danny_abra...@bmc.com>> wrote: Thanks again. Here is the example: >>>>>>>> dba-tlv-x6y64k% cat pg_hba.conf # TYPE DATABASE USER CIDR-ADDRESS METHOD local all all trust host all all 0.0.0.0/0<https://urldefense.com/v3/__http:/0.0.0.0/0__;!!PEZBYkTc!e_x_LCIABYSpqVum5S6Hr0TtEs6P4NaumHqEqyXEa3ErrZTPMmnUeC33JmyNsqr1kGf2DxtZKMbJ_ofkSSjZQC4hsuUN$> scram-sha-256 dba-tlv-x6y64k% pg_ctl reload server signaled dba-tlv-x6y64k% psql -Upostgres Password for user postgres: psql (17.4) Type "help" for help. ctrlmdb=# >>>>>>> PSQL should not have asked for the password. Thanks Danny Suggests there are environment variables coming into play making non-default choices for you. Namely, making you not use local as the connection method. David J.
