Thank you very much @Adrian Klaver .
On Tue, Jul 11, 2023 at 7:32 PM Adrian Klaver
wrote:
> On 7/11/23 14:45, Johnathan Tiamoh wrote:
> > Hello Adrian
> >
> > 1) PgBouncer version.
> >
> > pgbouncer.1.7.2
>
> PgBouncer most recent version is from here:
>
> http://www.pgbouncer.org/changelog.htm
This also sounds like a fairly advanced setup and a corporate environment.
Postgresql offers paid support and you probably want that.
Thanks,
Ben
On Tue, Jul 11, 2023, 4:33 PM Adrian Klaver
wrote:
> On 7/11/23 14:45, Johnathan Tiamoh wrote:
> > Hello Adrian
> >
> > 1) PgBouncer version.
> >
> >
On 7/11/23 14:45, Johnathan Tiamoh wrote:
Hello Adrian
1) PgBouncer version.
pgbouncer.1.7.2
PgBouncer most recent version is from here:
http://www.pgbouncer.org/changelog.html
PgBouncer 1.19.x
2023-05-31 - PgBouncer 1.19.1 - “Sunny Spring”
And since 1.7.x there have been these related
Hello Adrian
1) PgBouncer version.
pgbouncer.1.7.2
2) Did you change the settings when going from 9.5 to 14.8?
No. I did not do any configuration changes on the bouncers
3) Does the PgBouncer log show anything relevant?
No. It does not show anything
4) Does '...through the pgbouncers...' me
On 7/11/23 08:53, Johnathan Tiamoh wrote:
I can connect.
All applications and other users that connect from to the databases
through the pgbouncers can't connect.
That would have been a good thing to have mentioned in your first post.
I don't use PgBouncer so I am not going to be of much us
I can connect.
All applications and other users that connect from to the databases through
the pgbouncers can't connect.
On Tue, Jul 11, 2023 at 11:46 AM Adrian Klaver
wrote:
> On 7/10/23 20:45, Laurenz Albe wrote:
> > On Mon, 2023-07-10 at 20:38 -0400, Johnathan Tiamoh wrote:
> >> Below is th
On 7/10/23 20:45, Laurenz Albe wrote:
On Mon, 2023-07-10 at 20:38 -0400, Johnathan Tiamoh wrote:
Below is the full error message.
2023-06-27 05:01:27.385 CDT| XXX (60930)|
APPNAME=[unknown]| DB=postgres| USER=grafana| PID=9061| 1| authentication|
PGE-28P01: FATAL: passwor
Hello KK,
In the beginning, it was a little challenging, but as the process went on
it became easy. No, it was not a multistage upgrade. It was possible to
upgrade straight from 9.5 to 14.
We did not change anything on the schema. For data type, we alter all
tables that were created with OIDs to
On Mon, 2023-07-10 at 20:38 -0400, Johnathan Tiamoh wrote:
> Below is the full error message.
>
> 2023-06-27 05:01:27.385 CDT| XXX (60930)|
> APPNAME=[unknown]| DB=postgres| USER=grafana| PID=9061| 1| authentication|
> PGE-28P01: FATAL: password authentication failed for use
Sorry Adrian,
Below is the full error message.
2023-06-27 05:01:27.385 CDT| XXX (60930)|
APPNAME=[unknown]| DB=postgres| USER=grafana| PID=9061| 1| authentication|
PGE-28P01: FATAL: password authentication failed for user "grafana"
2023-06-27 05:01:27.385 CDT| XXX
On 7/10/23 13:20, Johnathan Tiamoh wrote:
Ok Adrian,
Postgres 9.5
postgresql.conf
password_encryption = ? md5 > wish is the default for 9.5
pg_hba.conf -> md5
Provide the relevant lines
Postgres 14.8
postgresql.conf
> Ok Adrian,
>
> Postgres 9.5
>
> postgresql.conf
>
> password_encryption = ? md5 > wish is the default for 9.5
>
> pg_hba.conf-> md5
>
> Provide the relevant lines
>
> Postgres 14.8
>
> postgresql.conf
>
> password_encryption = ?
Ok Adrian,
Postgres 9.5
postgresql.conf
password_encryption = ? md5 > wish is the default for 9.5
pg_hba.conf-> md5
Provide the relevant lines
Postgres 14.8
postgresql.conf
password_encryption = ? scram-sha-256 > wish is t
On 7/10/23 12:55, Johnathan Tiamoh wrote:
Please reply to list also.
Ccing list
Ok Adrian,
Postgres 9.5
postgresql.conf
password_encryption = ? md5 > wish is the default for 9.5
pg_hba.conf -> md5
Provide the relevant lines
Postgres 14.
On 7/10/23 11:15, Johnathan Tiamoh wrote:
Hello,
I upgraded from postgresql 9.5 to 14.8. After the upgrade users were not
able to connect due to password hash.
The password encryption was on scram-sha-256. The password hash was on
md5. in the pg_hba.conf file the authentication method was md
15 matches
Mail list logo
