| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Report roles in pg_upgrade pg_ prefix check |
| Date: | 2022-11-25 20:20:02 |
| Message-ID: | Y4EjcmIl+IGBa5J+@momjian.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Nov 24, 2022 at 12:31:09PM +0100, Daniel Gustafsson wrote:
> Looking at a recent pg_upgrade thread I happened to notice that the check for
> roles with a pg_ prefix only reports the error, not the roles it found. Other
> similar checks where the user is expected to alter the old cluster typically
> reports the found objects in a textfile. The attached adds reporting to make
> that class of checks consistent (the check for prepared transactions which also
> isn't reporting is different IMO as it doesn't expect ALTER commands).
>
> As this check is only executed against the old cluster the patch removes the
> check when printing the error.
+1
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Embrace your flaws. They make you human, rather than perfect,
which you will never be.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Borisov | 2022-11-25 21:10:57 | Re: Use fadvise in wal replay |
| Previous Message | Alvaro Herrera | 2022-11-25 19:58:19 | Re: Fix for visibility check on 14.5 fails on tpcc with high concurrency |