Re: Memory Context problems... - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Memory Context problems...
Date
Msg-id 23401.1099855875@sss.pgh.pa.us
Whole thread Raw
In response to Memory Context problems...  ("Katsaros Kwn/nos" <ntinos@aueb.gr>)
Responses Re: Memory Context problems...  ("Katsaros Kwn/nos" <ntinos@aueb.gr>)
List pgsql-hackers
"Katsaros Kwn/nos" <ntinos@aueb.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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_arch.c call to sleep()
Next
From: Andrew Dunstan
Date:
Subject: Re: pg_arch.c call to sleep()