> On 29 Nov 2022, at 00:24, Michael Paquier wrote:
>
> On Mon, Nov 28, 2022 at 09:58:46AM +0100, Daniel Gustafsson wrote:
>> We are a bit inconsistent in how much details we include in the report
>> textfiles, so could do that without breaking any consistency in reporting.
>> Looking at other che
On Mon, Nov 28, 2022 at 09:58:46AM +0100, Daniel Gustafsson wrote:
> We are a bit inconsistent in how much details we include in the report
> textfiles, so could do that without breaking any consistency in reporting.
> Looking at other checks, the below format would match what we already do
> fair
> On 28 Nov 2022, at 02:18, Michael Paquier wrote:
>
> 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
>> simil
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 ty
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 ty
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 repor
