What I am looking for is the version in which this problem has been
resolved.
I can't find it anywhere in the documentation.
-----Original Message-----
From: pgsql-general-owner@postgresql.org
[mailto:pgsql-general-owner@postgresql.org] On Behalf Of David Fetter
Sent: January 07, 2009 8:32 PM
To: yogvinder
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] RCA for MemoryContextAlloc: invalid request
size(Known Issue)
On Wed, Jan 07, 2009 at 06:07:02AM -0800, yogvinder wrote:
>
> Hi All,
>
> I am having multiple postgresql 7.3(pretty old version now) on rhel4
> servers.
Not just "pretty old," but past any community support. You'll need to
build and implement an upgrade strategy along with doing your upgrade.
> I am getting the error MemoryContextAlloc: invalid request size on
> many of these servers from time to time.
>
> On crawling through net, I have found that its because of some bad
> word value in a variable length field which implies database
> corruption. A possible solution to recover database is by deleting
> the corrupted row and then continuing till all the bad rows are
> deleted.
>
> My Queries: 1) What is the root cause? Why database is getting
> corrupted.
The root cause is that whoever was responsible for this cluster failed
to upgrade to a supported version. Don't Do That Again :)
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
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Disclaimer :- This e-mail and any attachment may contain confidential, proprietary or legally privileged information.
Ifyou 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.
NewgenSoftware Technologies Ltd (NSTL) accepts no responsibilities for loss or damage arising from the use of the
informationtransmitted by this email including damages from virus and further acknowledges that no binding nature of
themessage shall be implied or assumed unless the sender does so expressly with due authority of NSTL.
