| From: | "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com> |
|---|---|
| To: | "Yogvinder Singh" <yogvinder(at)newgen(dot)co(dot)in> |
| Cc: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>, "Stefan Kaltenbrunner" <stefan(at)kaltenbrunner(dot)cc>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: RCA for MemoryContextAlloc: invalid request size(Known Issue) |
| Date: | 2009-01-09 09:28:30 |
| Message-ID: | 2e78013d0901090128o132ba3b0j9eec3e345cd7155d@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Jan 9, 2009 at 2:53 PM, Yogvinder Singh <yogvinder(at)newgen(dot)co(dot)in> wrote:
> That I'll do but that still won't answer the question : What is the reason
> for the data corruption leading to " MemoryContextAlloc: invalid request
> size"
>
That's because you may read the corrupt data and do further operations
which leads to failure. For example, the tuple length may be corrupted
and you try to copy that tuple to memory. That's when the palloc can
fail with the error.
Thanks,
Pavan
--
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yogvinder Singh | 2009-01-09 10:47:09 | Re: RCA for MemoryContextAlloc: invalid request size(Known Issue) |
| Previous Message | Yogvinder Singh | 2009-01-09 09:23:24 | Re: RCA for MemoryContextAlloc: invalid request size(Known Issue) |