Thread: Regular issues faced on postgres 8.1
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.
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
On Fri, Jan 21, 2011 at 12:37:19PM +0530, Kunwar Anjani Tyagi wrote: > Server Details : > > Environment : RHEL 4 > Postgres Version :Postgres 8.1 While you would normally need to supply the full version number, as in 8.1.24, you've supplied enough info with the major version, 8.1, which just went end-of-life, i.e. it's no longer supported by the community. > 1.. Missing chunk number 0 for toast value : This case is generated due to corruption of toast table of a particulartable.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 automaticallygenerated , how-ever the "oids " still remains different (In some of the cases, oids also same). If a thereis 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 fileis missing. After analyzing it is found that file itself is missing. To resolve this we need to create blank files paddedwith zero, resulting in data loss. > Note : The above given problems are mostly on the tables which have high frequency of update. Move to 8.2.19 right away, then start testing your application stack with 9.0.2 (more generally 9.0.latest, whatever "latest" is). The 8.2 branch is supported through December of this year, which should help with your immediate problem. http://wiki.postgresql.org/wiki/PostgreSQL_Release_Support_Policy The 8.2 series doesn't fix the "automatic cast to text" issue which drives the thorough testing you'll need to do with the 9.0 series. Check very carefully here for potential incompatibilities with each major (8.4 -> 9.0) and, to a lesser extent, minor (9.0.1->9.0.2, e.g.) version upgrade. http://www.postgresql.org/docs/current/static/release.html You'll also want to make some kind of plans to build major version upgrades into your development process, as end-of-life is a fact of life in this as in every other software or system. Cheers, David. -- David Fetter <david@fetter.org> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fetter@gmail.com iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate