Re: pg_upgrade --logfile option documentation - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: pg_upgrade --logfile option documentation
Date
Msg-id 20120229230229.GA7005@momjian.us
Whole thread Raw
In response to Re: pg_upgrade --logfile option documentation  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: pg_upgrade --logfile option documentation  ("A.M." <agentm@themactionfaction.com>)
Re: pg_upgrade --logfile option documentation  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Wed, Feb 29, 2012 at 04:34:24PM -0500, Robert Haas wrote:
> On Tue, Feb 28, 2012 at 9:45 PM, Bruce Momjian <bruce@momjian.us> wrote:
> > OK, I have implemented both Roberts and Àlvaro's ideas in my patch.
> > I only add the .old suffix to pg_controldata when link mode is used, and
> > I now do it after the schema has been created (the most common failure
> > case for pg_upgrade), and just before we actually link files --- both
> > very good ideas.
> 
> Thanks for working on this.  I think this will be a significant
> usability improvement.

Glad I got such good feedback and ideas.

> Any ideas about improving the error reporting more generally, so that
> when reloading the dump fails, the user can easily see what went
> belly-up, even if they didn't use -l?

The only idea I have is to write the psql log to a temporary file and
report the last X lines from the file in case of failure.  Does that
help?

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Parameterized-path cost comparisons need some work
Next
From: Nathan Boley
Date:
Subject: Re: Collect frequency statistics for arrays