Re: Memory Context problems...

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Katsaros Kwn/nos" <ntinos(at)aueb(dot)gr>
Cc: Postgres Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Memory Context problems...
Date: 2004-11-07 19:31:15
Message-ID: 23401.1099855875@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Katsaros Kwn/nos" <ntinos(at)aueb(dot)gr> writes:
> More precisely,when I call (my_)SPI_prepare the following message comes
> exactly at the point where (my_)SPI_end_call(true) is called:

> WARNING: problem in alloc set my_SPI Exec: detected write past chunk
> end in block 0x830b7e8, chunk 0x830c058
> WARNING: problem in alloc set my_SPI Exec: detected write past chunk
> end in block 0x8307720, chunk 0x830b6cc

> Any ideas? I think it is something with the memory contexts but
> obviously this is not enough to solve the problem.

I'd bet on buffer-overrun problems. Check your allocation request sizes
against what's actually being used.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2004-11-07 20:01:14 Re: pg_arch.c call to sleep()
Previous Message Tom Lane 2004-11-07 19:28:20 Re: pg_arch.c call to sleep()