Thread: unsubscrib

unsubscrib

From
Rodrigo De la Peña
Date:
[ADMIN] unsubscrib

please remove me from the list

_________________________________________________________
Do You Yahoo!?
Información de Estados Unidos y América Latina, en Yahoo! Noticias.
Visítanos en http://noticias.espanol.yahoo.com

Recovery assistence....

From
"Marc Mitchell"
Date:
Running 7.3.2 under RedHat we suffered a disk crash.  Following was
Postgres log output from after crash:


2003-09-04 08:46:12 [29550]  LOG:  connection authorized: user=postgres
database=gts
Found a pre-existing shared memory block (key 5434001, id 65538) still
in use.
If you're sure there are no old backends still running,
remove the shared memory block with ipcrm(1), or just
delete "/u3/pgsql/7.3.2/data/postmaster.pid".
2003-09-04 09:24:51 [1873]   LOG:  database system was interrupted at
2003-09-04 08:45:59 CDT
2003-09-04 09:24:51 [1873]   LOG:  checkpoint record is at 0/B31378B4
2003-09-04 09:24:51 [1873]   LOG:  redo record is at 0/B3129C68; undo
record is at 0/0; shutdown FALSE
2003-09-04 09:24:51 [1873]   LOG:  next transaction id: 2675704; next
oid: 3607454
2003-09-04 09:24:51 [1873]   LOG:  database system was not properly shut
down; automatic recovery in progress
2003-09-04 09:24:51 [1873]   LOG:  redo starts at 0/B3129C68
2003-09-04 09:24:51 [1873]   PANIC:  Invalid page header in block 2696
of 329110
2003-09-04 09:24:51 [1870]   LOG:  startup process (pid 1873) was
terminated by signal 6
2003-09-04 09:24:51 [1870]   LOG:  aborting startup due to startup
process failure
2003-09-04 09:25:50 [1934]   LOG:  database system was interrupted being
in recovery at 2003-09-04 09:24:51 CDT
    This probably means that some data blocks are corrupted
    and you will have to use the last backup for recovery.


Question: is there any way to force consistency?  This is a development
database so the main things we need are the schemas which were not
changing at time of the crash.  The data can be recovered from System
Test scripts.  We're looking to do something quicker than a recovery
from a backup.

Any input would be appreciated.

Marc Mitchell - Senior Application Architect
Enterprise Information Solutions, Inc.
Donwers Grove, IL 60515
marcm@eisolution.com




-----Original Message-----
From: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Rodrigo De la
Peña
Sent: Thursday, September 04, 2003 7:45 AM
To: pgsql-admin@postgresql.org
Subject: [ADMIN] unsubscrib


[ADMIN] unsubscrib

please remove me from the list

_________________________________________________________
Do You Yahoo!?
Información de Estados Unidos y América Latina, en Yahoo! Noticias.
Visítanos en http://noticias.espanol.yahoo.com

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend


Re: Recovery assistence....

From
Tom Lane
Date:
"Marc Mitchell" <marcm@eisolution.com> writes:
> Running 7.3.2 under RedHat we suffered a disk crash.  Following was
> Postgres log output from after crash:

> 2003-09-04 09:24:51 [1873]   LOG:  redo starts at 0/B3129C68
> 2003-09-04 09:24:51 [1873]   PANIC:  Invalid page header in block 2696
> of 329110

Try updating to 7.3.4 --- it gets out of some startup problems that
earlier 7.3.* releases fail to cope with.  If that doesn't help,
I think your next step is "pg_resetxlog".

            regards, tom lane