pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Manoj K P <manoj@comodo.com>
To: pgsql-admin@postgresql.org
Subject: Database corruption
Date: Mon, 14 Nov 2011 01:54:52 -0800 (PST)
Message-ID: <1321264492950-4990279.post@n5.nabble.com> (raw)

Due to Hard disk space issue on the WAL partition, database was down , When I
am going to start postgres  again ,got following error message

This DB is grater than 1 TB  restore will take long time , any other way
other than pg_resetxlog ?


Nov 14 04:32:41 dbname postgres[4384]: [2-1] 2011-11-14 04:32:41.423 EST
4384 LOG:  invalid record length at 500C/5EFFF2B8
Nov 14 04:32:41 dbname postgres[4384]: [3-1] 2011-11-14 04:32:41.423 EST
4384 LOG:  invalid primary checkpoint record
Nov 14 04:32:41 dbname postgres[4384]: [4-1] 2011-11-14 04:32:41.423 EST
4384 LOG:  invalid resource manager ID in secondary checkpoint record
Nov 14 04:32:41 dbname postgres[4384]: [5-1] 2011-11-14 04:32:41.423 EST
4384 PANIC:  could not locate a valid checkpoint record
Nov 14 04:32:41 dbname postgres[4383]: [1-1] 2011-11-14 04:32:41.424 EST
4383 LOG:  startup process (PID 4384) was terminated by signal 6: Aborted
Nov 14 04:32:41 dbname postgres[4383]: [2-1] 2011-11-14 04:32:41.424 EST
4383 LOG:  aborting startup due to startup process failure




pg_controldata : Result is


pg_control version number:            843
Catalog version number:               200904091
Database system identifier:           5404099570172901375
Database cluster state:               in production
pg_control last modified:             Mon 14 Nov 2011 01:02:51 AM EST
Latest checkpoint location:           500C/5EFFF2B8
Prior checkpoint location:            500C/5EFFF270
Latest checkpoint's REDO location:    500C/5EFFF2B8
Latest checkpoint's TimeLineID:       10000
Latest checkpoint's NextXID:          1/2784291602
Latest checkpoint's NextOID:          63034795
Latest checkpoint's NextMultiXactId:  1658683101
Latest checkpoint's NextMultiOffset:  3632122117
Time of latest checkpoint:            Mon 14 Nov 2011 01:02:51 AM EST
Minimum recovery ending location:     0/0
Maximum data alignment:               8
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
Maximum size of a TOAST chunk:        1996
Date/time type storage:               64-bit integers
Float4 argument passing:              by value
Float8 argument passing:              by value



--
View this message in context: http://postgresql.1045698.n5.nabble.com/Database-corruption-tp4990279p4990279.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.



view thread (9+ messages)

Message-ID: <1321264492950-4990279.post@n5.nabble.com>
Permalink:  ../1321264492950-4990279.post@n5.nabble.com/
Also on:    postgresql.org/message-id/1321264492950-4990279.post@n5.nabble.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: manoj@comodo.com
  Subject: Re: Database corruption
  In-Reply-To: <1321264492950-4990279.post@n5.nabble.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox