On Fri, Jan 21, 2011 at 2:07 AM, Kunwar Anjani Tyagi
<kunwar.tyagi@newgen.co.in> wrote:
> Missing chunk number 0 for toast value : This case is generated due to
> corruption of toast table of a particular table.Many times reindexing the
> toast table solves the problem.
> Cannot insert a duplicate key into unique index : On analysing this case =
we
> found that=A0=A0duplicate rows =A0get automatically generated , how-ever =
the
> "oids=A0" still remains different (In some of the cases, oids also same).=
=A0If
> a there is a primary key constarint on a column=A0, then =A0this conditio=
n gets
> violated and start throwing error.
> Missing file in clog directory : While doing operations on some records,
> Error comes that an offset of clog file is missing. After analyzing it is
> found that file itself is missing. To resolve this we need to create blank
> files padded with zero, resulting in data loss.
It sounds to me like you have a bad case of filesystem corruption. I
would start by checking your hardware.
PostgreSQL 8.1 is no longer officially supported, and no further bug
fixes will be released. Both performance and reliability of newer
releases are much improved; however, none of that will help you if you
have bad hardware.
--=20
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
