From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Tory M Blue <tmblue(at)gmail(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Odd postgres12 upgrade is changing or munging a password? |
Date: | 2020-05-08 19:16:18 |
Message-ID: | e3c46a33-67e9-1083-4706-e95a77c46079@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 5/8/20 12:11 PM, Tory M Blue wrote:
>
>
> On Thu, May 7, 2020 at 11:41 PM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at
> <mailto:laurenz(dot)albe(at)cybertec(dot)at>> wrote:
>
> On Thu, 2020-05-07 at 11:55 -0700, Tory M Blue wrote:
> > Going from 9.5 to 12 and 2 times now, I've had a password either
> go missing or munged.
> > I've had to add an alter statement at the end of the upgrade.
> >
> > The DB is functioning fine, shut it down, do the upgrade and the
> password is munged.
> > Seems like an odd occurrence, we have not noted any other weird
> issues.
> >
> > Anyone else see or hear of this?
>
> The only explanation I can come up with is that
> "password_encryption" is set to
> "scram-sha-256" on the v12 server.
>
> Yours,
> Laurenz Albe
> --
> Cybertec | https://www.cybertec-postgresql.com
>
>
> If that was the case, wouldn't it change the others as well? Why a
> single password.
I would first confirm what password_encryption in postgresql.conf is set
to. By default it is set to 'md5'.
>
> Super strange indeed :)
>
> Tory
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2020-05-08 19:18:59 | Re: pg_basebackup cannot compress to STDOUNT |
Previous Message | Support | 2020-05-08 19:14:56 | pg_basebackup cannot compress to STDOUNT |