| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Giving more detail in pg_upgrade errormessage |
| Date: | 2023-07-18 14:59:32 |
| Message-ID: | E0D5EA16-A085-4753-8DDC-C7055048B439@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)mail(dot)gmail(dot)com
| Attachment | Content-Type | Size |
|---|---|---|
| pg_upgrade_controldata.diff | application/octet-stream | 735 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mingli Zhang | 2023-07-18 15:17:24 | Re: Giving more detail in pg_upgrade errormessage |
| Previous Message | Tom Lane | 2023-07-18 14:50:49 | Re: Increase limit on max length of the password( pg versions < 14) |