Giving more detail in pg_upgrade errormessage - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Giving more detail in pg_upgrade errormessage
Date
Msg-id E0D5EA16-A085-4753-8DDC-C7055048B439@yesql.se
Whole thread Raw
Responses Re: Giving more detail in pg_upgrade errormessage
Re: Giving more detail in pg_upgrade errormessage
List pgsql-hackers
Looking at the upgrade question in [0] made me realize that we discard
potentially useful information for troubleshooting.  When we check if the
cluster is properly shut down we might as well include the status from
pg_controldata in the errormessage as per the trivial (but yet untested)
proposed diff.

Is there a reason not to be verbose here as users might copy/paste this output
when asking for help?

--
Daniel Gustafsson

[0] CACoPQdbQTysF=EKckyFNGTdpOdXXMEsf_2ACno+bcNqQCB5raA@mail.gmail.com


Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Increase limit on max length of the password( pg versions < 14)
Next
From: Mingli Zhang
Date:
Subject: Re: Giving more detail in pg_upgrade errormessage