Re: Report roles in pg_upgrade pg_ prefix check

From: Michael Paquier <michael(at)paquier(dot)xyz>
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-28 01:18:53
Message-ID: Y4QMfaPRxpEyIgNy@paquier.xyz
Views: Raw Message | Whole Thread | 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. A backpatch would be nice, though not strictly mandatory as
that's not a bug fix.

+ ntups = PQntuples(res);
+ i_rolname = PQfnumber(res, "rolname");

Would it be worth adding the OID on top of the role name in the
generated report? That would be a free meal.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2022-11-28 02:13:23 Fix comment in SnapBuildFindSnapshot
Previous Message Masahiko Sawada 2022-11-28 01:13:28 Re: [BUG] FailedAssertion in SnapBuildPurgeOlderTxn