Skip site navigation (1) Skip section navigation (2)

Regular issues faced on postgres 8.1

From: "Kunwar Anjani Tyagi" <kunwar(dot)tyagi(at)newgen(dot)co(dot)in>
To: <pgsql-bugs(at)postgresql(dot)org>
Cc: <utsav(dot)turray(at)newgen(dot)co(dot)in>,<deo(dot)bhardwaj(at)newgen(dot)co(dot)in>
Subject: Regular issues faced on postgres 8.1
Date: 2011-01-21 07:07:19
Message-ID: 05A01B4BE1254B2EB4606AB4448C9448@central.newgen.local (view raw or flat)
Thread:
Lists: 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 to corruption of toast table of a particular table.Many times reindexing the toast table solves the problem. 
  2.. Cannot insert a duplicate key into unique index : On analysing this case we found that  duplicate rows  get automatically generated , how-ever the "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. 
  3.. 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. 
 Note : The above given problems are mostly on the tables which have high frequency of update.  

Kindly help us in resolving these issues, Whether these are bugs resolved in latest versions of postgres, If so than in which version, above stated problems are resolved.
 



Regards
Kunwar Anjani Tyagi
Disclaimer :- This e-mail and any attachment may contain confidential, proprietary or legally privileged information. If you are not the original intended recipient and have erroneously received this message, you are prohibited from using, copying, altering or disclosing the content of this message. Please delete it immediately and notify the sender. Newgen Software Technologies Ltd (NSTL)  accepts no responsibilities for loss or damage arising from the use of the information transmitted by this email including damages from virus and further acknowledges that no binding nature of the message shall be implied or assumed unless the sender does so expressly with due authority of NSTL.


Responses

pgsql-bugs by date

Next:From: Magnus HaganderDate: 2011-01-21 10:24:02
Subject: Re: Is there a way to build PostgreSQL client libraries with MinGW
Previous:From: Andrew DunstanDate: 2011-01-21 03:06:06
Subject: Re: Is there a way to build PostgreSQL client libraries with MinGW

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group