Re: Giving more detail in pg_upgrade errormessage

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Giving more detail in pg_upgrade errormessage
Date: 2023-07-18 16:04:20
Message-ID: 57271.1689696260@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Daniel Gustafsson <daniel(at)yesql(dot)se> writes:
> 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?

Agreed, but I think you need to chomp the string's trailing newline,
or it'll look ugly. You might as well do that further up and remove
the newlines from the comparison strings, too.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2023-07-18 16:05:11 Re: Inefficiency in parallel pg_restore with many tables
Previous Message Alvaro Herrera 2023-07-18 15:53:13 Re: remaining sql/json patches