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

Re: Unfamiliar recovery message afer server crash

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Arthur Ward" <award(at)dominionsciences(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Unfamiliar recovery message afer server crash
Date: 2004-04-21 03:07:55
Message-ID: 25207.1082516875@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-admin
"Arthur Ward" <award(at)dominionsciences(dot)com> writes:
> Apr 20 11:28:14 postgres: [6203] LOG:  database system was not properly
> shut down; automatic recovery in progress
> Apr 20 11:28:14 postgres: [6203] LOG:  redo starts at 7C/CF55FBAC
> Apr 20 11:28:17 postgres: [6203] LOG:  unexpected pageaddr 7C/C7A0A000 in
> log file 124, segment 207, offset 10526720
> Apr 20 11:28:17 postgres: [6203] LOG:  redo done at 7C/CFA09F7C
> Apr 20 11:28:20 postgres: [6203] LOG:  database system is ready

> What's the significance of the "unexpected pageaddr" item?

Just that the first indication of end-of-XLOG was finding a stale page
header in a recycled XLOG file.  The above looks fine to me.  (The XLOG
recovery code tends to err on the side of verboseness... there are a lot
of messages it can print that might boggle a novice but are not really
indicative of problems.)

			regards, tom lane

In response to

pgsql-admin by date

Next:From: Tom LaneDate: 2004-04-21 03:29:02
Subject: Re: pg_autovacuum crashes when query fails for temp
Previous:From: Christopher BrowneDate: 2004-04-21 02:24:21
Subject: Re: pg_autovacuum crashes when query fails for temp

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