Regular issues faced on postgres 8.1 - Mailing list pgsql-bugs

From Kunwar Anjani Tyagi
Subject Regular issues faced on postgres 8.1
Date
Msg-id 05A01B4BE1254B2EB4606AB4448C9448@central.newgen.local
Whole thread Raw
Responses Re: Regular issues faced on postgres 8.1
Re: Regular issues faced on postgres 8.1
List pgsql-bugs
Server Details :

Environment : RHEL 4
Postgres Version :Postgres 8.1
  1.. Missing chunk number 0 for toast value : This case is generated due t=
o corruption of toast table of a particular table.Many times reindexing the=
 toast table solves the problem.=20
  2.. Cannot insert a duplicate key into unique index : On analysing this c=
ase we found that  duplicate rows  get automatically generated , how-ever t=
he "oids " still remains different (In some of the cases, oids also same). =
 If a there is a primary key constarint on a column , then  this condition =
gets violated and start throwing error.=20
  3.. Missing file in clog directory : While doing operations on some recor=
ds, 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 bla=
nk files padded with zero, resulting in data loss.=20
 Note : The above given problems are mostly on the tables which have high f=
requency of update.=20=20

Kindly help us in resolving these issues, Whether these are bugs resolved i=
n latest versions of postgres, If so than in which version, above stated pr=
oblems are resolved.
=20



Regards
Kunwar Anjani Tyagi
Disclaimer :- This e-mail and any attachment may contain confidential, prop=
rietary or legally privileged information. If you are not the original inte=
nded recipient and have erroneously received this message, you are prohibit=
ed from using, copying, altering or disclosing the content of this message.=
 Please delete it immediately and notify the sender. Newgen Software Techno=
logies Ltd (NSTL)  accepts no responsibilities for loss or damage arising f=
rom the use of the information transmitted by this email including damages =
from virus and further acknowledges that no binding nature of the message s=
hall be implied or assumed unless the sender does so expressly with due aut=
hority of NSTL.

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Psql malloc error on Git master
Next
From: Bernd Helmle
Date:
Subject: Re: Psql malloc error on Git master