| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Domen Šetar <domen(dot)setar(at)izum(dot)si>, "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Function problem |
| Date: | 2024-08-27 04:37:01 |
| Message-ID: | 0afce79b7fa0061e5f07199f88dd7f052c6eab81.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Tue, 2024-08-13 at 09:56 +0000, Domen Šetar wrote:
> I’m using pgbouncer in my postgresql installation. For authorization purposese I use function
> public.lookup (https://www.cybertec-postgresql.com/en/pgbouncer-authentication-made-easy/)
> which is defined for each database. Since we upgraded postgresql from V14 to V16 I have
> problems when migrating database from one instance to another: authentication doesn’t work.
> I have to drop function and define it again on database to make authentication work. Any idea why ?
I guess that my article is at fault. It still refers to "md5" authentication rather than
"scram-sha-256", which has been the password authenticatoin method of choice for years now.
I have updated my article.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Domen Šetar | 2024-08-27 08:00:15 | Unexpected authentication behaviour |
| Previous Message | Laurenz Albe | 2024-08-27 04:17:39 | Re: LIsten Errror |