Alexandra Nitzschke <[EMAIL PROTECTED]> writes:
> since our last report at 15.02.2008 we again encountered database errors:
> Livesystem:
> 30.04.2008 ERROR: invalid page header in block 12324 of relation "tzf_taf_fk"
> --
>
Hi,
since our last report at 15.02.2008 we again encountered database errors:
Livesystem:
30.04.2008 ERROR: invalid page header in block 12324 of relation "tzf_taf_fk"
--
- 12.09.2008 Update postgres from 8.1.3 to 8.3.3.
--
Alexandra Nitzschke napsal(a):
We went on with analyzing:
- the table was created at 2008/01/03 17:56h
- the nightly dump started at 2008/01/03 22:00h
- it tried to copy the table 'adresse_080103' at 22:00:08
- the dump crashed at 22:32:10 ( because of the error we reported
2007/12/14; we re
We did some analyzing and found out some mysterious things.
First we used the pg_check tool to analyze the table.
The result is:
# select pgcheck_page( 211593798 );
WARNING: relation 'adresse_080103', tuple (46,11): start of tuple is not
aligned properly
WARNING: relation 'adresse_080103', tu
Alexandra Nitzschke napsal(a):
Hi,
we retrieved again a database error:
pg_dump: Error message from server: ERROR: could not access status of
transaction 2926020847
DETAIL: Could not open file "pg_clog/0AE6": Datei oder Verzeichnis
nicht gefunden.
pg_dump: The command was: COPY public.adres
Hi,
we retrieved again a database error:
pg_dump: Error message from server: ERROR: could not access status of
transaction 2926020847
DETAIL: Could not open file "pg_clog/0AE6": Datei oder Verzeichnis nicht
gefunden.
pg_dump: The command was: COPY public.adresse_080103 (id, adr_id, adt_id,