unexpected pageaddr on startup/recovery

From: "Jim Buttafuoco" <jim(at)contactbda(dot)com>
To: "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: unexpected pageaddr on startup/recovery
Date: 2005-08-06 18:20:32
Message-ID: 20050806181751.M97078@contactbda.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hackers,

I had a system crash today. When Postgresql started I had the following in my pg.log file.

2005-08-06 14:14:26 [3352] LOG: database system was interrupted at 2005-08-06 11:57:28 EDT
2005-08-06 14:14:26 [3352] LOG: checkpoint record is at 5E5/9CAEA594
2005-08-06 14:14:26 [3352] LOG: redo record is at 5E5/9C6796A0; undo record is at 0/0; shutdown FALSE
2005-08-06 14:14:26 [3352] LOG: next transaction ID: 6273726; next OID: 4274112431
2005-08-06 14:14:26 [3352] LOG: database system was not properly shut down; automatic recovery in progress
2005-08-06 14:14:26 [3352] LOG: redo starts at 5E5/9C6796A0
2005-08-06 14:17:17 [3352] LOG: unexpected pageaddr 5E3/A7BFA000 in log file 1509, segment 171, offset 12558336
2005-08-06 14:17:17 [3352] LOG: redo done at 5E5/ABBF978C

Should I worry about the unexpected pageaddr message? and if so, what do I need to do

select version();
version
-------------------------------------------------------------------------------------------------
PostgreSQL 7.4.5 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.3.4 (Debian 1:3.3.4-6sarge1)

Thanks
Jim

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Wong 2005-08-06 21:04:19 Re: [HACKERS] O_DIRECT for WAL writes
Previous Message Matteo Beccati 2005-08-06 13:22:42 Re: Enhanced containment selectivity function