| From: | Fabrice Chapuis <fabrice636861(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | roles management problem after upgrading in PG 17 |
| Date: | 2025-07-24 11:03:02 |
| Message-ID: | CAA5-nLAjVBt=C=K5VpkigKMbyBkVr2xGRkqtL8vxEgjOn07Z7Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
After upgrading from Postgres version 14 to Postgres version 17, I noticed
that some "grantor" roles (admin_role) disappear when exporting all roles
with grants
/usr/pgsql-17/bin/pg_dumpall --globals-only --quote-all-identifiers
--binary-upgrade --no-sync -f /var/lib/pgsql/roles_bin.sql
Consequently, the admin_role could not administer some roles in version 17
related to modifications made in version 16 concerning roles administration.
A message could be displayed when executing pg_upgrade with option --check
that the attribute "createrole" for a user is more restrictive since
version 16 and anomalies may appear after upgrading in the new version.
What is your opinion
Fabrice
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hayato Kuroda (Fujitsu) | 2025-07-24 11:19:02 | RE: recoveryStopsAfter is not usable when recovery_target_inclusive is false |
| Previous Message | Peter Eisentraut | 2025-07-24 11:02:57 | Re: Fixing MSVC's inability to detect elog(ERROR) does not return |