From: | Jim Nasby <decibel(at)decibel(dot)org> |
---|---|
To: | lim siang min <smlim916(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: how to resolve invalid primary checkpoint |
Date: | 2007-07-13 15:41:19 |
Message-ID: | 0E3C1683-0406-4D13-840B-E4BC093B3BA2@decibel.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Jul 10, 2007, at 4:08 AM, lim siang min wrote:
> I'm new to Postgresql and need to support on any IT related problem.
> One of my customer not able to start the postgresql services.
> The log said that ..
> record with zero length at 0/2E16910
> invalid primary checkpoint record
> record with zero length at 0/2E168D0
> invalid secondary checkpoint record
> panic: could not locate a valid checkpoint record.
>
> how should i resolve this issue.
> Really appreciate any inputs. Thanks.
Sounds like your WAL files have been corrupted, which indicates
faulty hardware (assuming that you haven't set fsync=off). I don't
really know if there's any way to recover from this; you may have to
restore from a backup. In any case, I'd question the hardware that
you're running on.
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2007-07-13 15:44:07 | Re: TOAST, large objects, and ACIDity |
Previous Message | Jim Nasby | 2007-07-13 15:39:29 | Re: Fastest way to join materalized view to child tables |