Re: Recovering database after disk crash

Поиск
Список
Период
Сортировка
От Vic Simkus
Тема Re: Recovering database after disk crash
Дата
Msg-id ce469da10805121418q2da729d7he568db41e217a95@mail.gmail.com
обсуждение исходный текст
Ответ на Recovering database after disk crash  ("Vic Simkus" <vic.simkus@gmail.com>)
Список pgsql-general
After doing some more reading I've come to the conclusion that I'm in
completely over my head.  I got a fresh copy of the corrupt data and
am starting from the very beginning.  Here's the error I get on
startup:

postgres@vsimkus-laptop:/usr/lib/postgresql/8.2/bin$ ./postgres  -D
/var/lib/postgresql/8.2/main
2008-05-12 16:16:02 CDT LOG:  could not load root certificate file
"root.crt": no SSL error reported
2008-05-12 16:16:02 CDT DETAIL:  Will not verify client certificates.
2008-05-12 16:16:02 CDT LOG:  database system was interrupted at
2008-04-16 09:28:36 CDT
2008-05-12 16:16:02 CDT LOG:  unexpected pageaddr 0/1114A000 in log
file 0, segment 17, offset 14295040
2008-05-12 16:16:02 CDT LOG:  invalid primary checkpoint record
2008-05-12 16:16:02 CDT LOG:  unexpected pageaddr 0/1114A000 in log
file 0, segment 17, offset 14295040
2008-05-12 16:16:02 CDT LOG:  invalid secondary checkpoint record
2008-05-12 16:16:02 CDT PANIC:  could not locate a valid checkpoint record
2008-05-12 16:16:02 CDT LOG:  startup process (PID 8359) was
terminated by signal 6
2008-05-12 16:16:02 CDT LOG:  aborting startup due to startup process failure

pg_control output:

 ./pg_controldata /var/lib/postgresql/8.2/main
pg_control version number:            822
Catalog version number:               200611241
Database system identifier:           5126483664462806975
Database cluster state:               in production
pg_control last modified:             Wed 16 Apr 2008 09:28:36 AM CDT
Current log file ID:                  0
Next log file segment:                18
Latest checkpoint location:           0/11DA3C38
Prior checkpoint location:            0/11DA3BF0
Latest checkpoint's REDO location:    0/11DA3C38
Latest checkpoint's UNDO location:    0/0
Latest checkpoint's TimeLineID:       1
Latest checkpoint's NextXID:          0/908105
Latest checkpoint's NextOID:          2001259
Latest checkpoint's NextMultiXactId:  7
Latest checkpoint's NextMultiOffset:  13
Time of latest checkpoint:            Wed 16 Apr 2008 09:13:56 AM CDT
Minimum recovery ending location:     0/0
Maximum data alignment:               4
Database block size:                  8192
Blocks per segment of large relation: 131072
WAL block size:                       8192
Bytes per WAL segment:                16777216
Maximum length of identifiers:        64
Maximum columns in an index:          32
Date/time type storage:               64-bit integers
Maximum length of locale name:        128
LC_COLLATE:                           en_US.UTF-8
LC_CTYPE:                             en_US.UTF-8

I ran pg_resetxlog in my previous mucking around, but that's when all
hell broke loose, so I'm holding off until someone more qualified
advises me to do so.

TIA

Vic

В списке pgsql-general по дате отправления:

Предыдущее
От: David Fetter
Дата:
Сообщение: Re: Making sure \timing is on
Следующее
От: Justin
Дата:
Сообщение: Re: rounding problems