Re: Problem with pg_upgrade - Mailing list pgsql-bugs

From Bruce Momjian
Subject Re: Problem with pg_upgrade
Date
Msg-id 20120706173153.GC6235@momjian.us
Whole thread Raw
In response to Problem with pg_upgrade  (Payal Singh <payals1@umbc.edu>)
List pgsql-bugs
On Fri, Jul 06, 2012 at 01:20:21PM -0400, Payal Singh wrote:
> Hi,
>
> I restored the backup on 9.1, made sure the database reached a consistent state
> and checkpointed. Then I performed the upgrade. Upgrade completed successfully
> but on running vacuumdb it gave the exact same error. The contents of log file
> are:
>
>
>  1. 2012-07-06 12:08:08 EDT [] [21723]: [1-1] user=,db=,e=00000: LOG:  database
>     system was interrupted while in recovery at log time 2012-07-03 03:07:02
>     EDT

Any idea why you are seeing the above "interrupted while in recovery"
message?

>  2. 2012-07-06 12:08:08 EDT [] [21723]: [2-1] user=,db=,e=00000: HINT:  If this
>     has occurred more than once some data might be corrupted and you might need
>     to choose an earlier recovery target.
>  3. 2012-07-06 12:08:08 EDT [] [21723]: [3-1] user=,db=,e=00000: LOG:  creating
>     missing WAL directory "pg_xlog/archive_status"
>  4. 2012-07-06 12:08:08 EDT [] [21723]: [4-1] user=,db=,e=00000: LOG:  database
>     system was not properly shut down; automatic recovery in progress

The above is also confusing.  pg_upgrade uses pg_ctl -w stop/start, so I
am confused, how it could show as recovering.

>
> Also, this time I did not run vacuumdb on old server before performing the
> upgrade.

I think you had better show us exactly what you are doing here --- how
you are setting up these clusters, how you are running pg_upgrade, what
commands you are typing, etc.

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +

pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: BUG #6716: memory of Autovacuum leak?
Next
From: Bruce Momjian
Date:
Subject: Re: Problem with pg_upgrade