Skip site navigation (1) Skip section navigation (2)

Re: pg_upgrade --logfile option documentation

From: "A(dot)M(dot)" <agentm(at)themactionfaction(dot)com>
To: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgrade --logfile option documentation
Date: 2012-02-29 23:22:27
Message-ID: C83960FF-D0ED-442C-9453-971156315E67@themactionfaction.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Feb 29, 2012, at 6:02 PM, Bruce Momjian wrote:

> 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(at)momjian(dot)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?
> 


Perhaps pg_upgrade can print the path to the temp file containing the log and instruct the user to look there for more detail.

Cheers,
M




In response to

Responses

pgsql-hackers by date

Next:From: Jim NasbyDate: 2012-02-29 23:38:24
Subject: Re: 16-bit page checksums for 9.2
Previous:From: Tom LaneDate: 2012-02-29 23:10:44
Subject: Re: Collect frequency statistics for arrays

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group