public inbox for [email protected]
help / color / mirror / Atom feedFrom: David G. Johnston <[email protected]>
To: Alpaslan AKDAĞ <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: Password Encryption and Connection Issues
Date: Wed, 9 Jul 2025 07:06:48 -0700
Message-ID: <CAKFQuwbtK4Pc4PZPOYe7spXZsjou7Q-md4n5mVUJv0HzKcd9KQ@mail.gmail.com> (raw)
In-Reply-To: <CAHKeUX8D-c=Y8su6eFLZXJ09VOVLnSUHYD-649NoXW8cHdBPhg@mail.gmail.com>
References: <CAHKeUX8D-c=Y8su6eFLZXJ09VOVLnSUHYD-649NoXW8cHdBPhg@mail.gmail.com>
On Wed, Jul 9, 2025 at 6:57 AM Alpaslan AKDAĞ <[email protected]>
wrote:
>
> 1. In such a case, what would be the recommended approach or best
> practice to follow during upgrades in order to avoid this kind of issue?
>
> This is all described quite clearly in the documentation, including the
upgrade procedure in the final paragraph.
https://www.postgresql.org/docs/current/auth-password.html
Given that pg_hba.conf still uses md5 I'm a bit confused regarding the
claim of some people being unable to authenticate; but you've provided
insufficient data to diagnose. In any case, hopefully you can just change
all passwords to use scram and move on.
David J.
view thread (8+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Password Encryption and Connection Issues
In-Reply-To: <CAKFQuwbtK4Pc4PZPOYe7spXZsjou7Q-md4n5mVUJv0HzKcd9KQ@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox