| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Alpaslan AKDAĞ <alpaslanakdag(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Password Encryption and Connection Issues |
| Date: | 2025-07-09 14:06:48 |
| Message-ID: | CAKFQuwbtK4Pc4PZPOYe7spXZsjou7Q-md4n5mVUJv0HzKcd9KQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Jul 9, 2025 at 6:57 AM Alpaslan AKDAĞ <alpaslanakdag(at)gmail(dot)com>
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Sabino Mullane | 2025-07-09 14:58:15 | Re: Password Encryption and Connection Issues |
| Previous Message | Jordan Adams | 2025-07-09 14:06:06 | PostgresSQL Setup error |