MIME-Version: 1.0
References: <CAHKeUX8D-c=Y8su6eFLZXJ09VOVLnSUHYD-649NoXW8cHdBPhg@mail.gmail.com>
In-Reply-To: <CAHKeUX8D-c=Y8su6eFLZXJ09VOVLnSUHYD-649NoXW8cHdBPhg@mail.gmail.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
Date: Wed, 9 Jul 2025 07:06:48 -0700
Message-ID: <CAKFQuwbtK4Pc4PZPOYe7spXZsjou7Q-md4n5mVUJv0HzKcd9KQ@mail.gmail.com>
Subject: Re: Password Encryption and Connection Issues
To: =?UTF-8?Q?Alpaslan_AKDA=C4=9E?= <alpaslanakdag@gmail.com>
Cc: "pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000b90d0e06397f98e0"
Archived-At: <https://www.postgresql.org/message-id/CAKFQuwbtK4Pc4PZPOYe7spXZsjou7Q-md4n5mVUJv0HzKcd9KQ%40mail.gmail.com>
Precedence: bulk

--000000000000b90d0e06397f98e0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, Jul 9, 2025 at 6:57=E2=80=AFAM Alpaslan AKDA=C4=9E <alpaslanakdag@g=
mail.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 issu=
e?
>
> 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.

--000000000000b90d0e06397f98e0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon=
t-family:arial,helvetica,sans-serif"><span style=3D"font-family:Arial,Helve=
tica,sans-serif">On Wed, Jul 9, 2025 at 6:57=E2=80=AFAM Alpaslan AKDA=C4=9E=
 &lt;<a href=3D"mailto:alpaslanakdag@gmail.com">alpaslanakdag@gmail.com</a>=
&gt; wrote:</span></div></div><div class=3D"gmail_quote gmail_quote_contain=
er"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><ol>=
<li>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?</li></ol><=
/div></blockquote><div><span class=3D"gmail_default" style=3D"font-family:a=
rial,helvetica,sans-serif">This is all described quite clearly in the docum=
entation, including the upgrade procedure in the final paragraph.</span></d=
iv><div><br></div><div class=3D"gmail_default" style=3D"font-family:arial,h=
elvetica,sans-serif"><a href=3D"https://www.postgresql.org/docs/current/aut=
h-password.html">https://www.postgresql.org/docs/current/auth-password.html=
</a></div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica=
,sans-serif"><br></div><div class=3D"gmail_default" style=3D"">Given that p=
g_hba.conf still uses md5 I&#39;m a bit confused regarding the claim of som=
e people being unable to authenticate; but you&#39;ve provided insufficient=
 data to diagnose.=C2=A0 In any case, hopefully you can just change all pas=
swords to use scram and move on.</div><div class=3D"gmail_default" style=3D=
"font-family:arial,helvetica,sans-serif"><span style=3D"font-family:Arial,H=
elvetica,sans-serif"><br></span></div><div class=3D"gmail_default" style=3D=
"font-family:arial,helvetica,sans-serif"><span style=3D"font-family:Arial,H=
elvetica,sans-serif">David J.</span></div></div></div>

--000000000000b90d0e06397f98e0--