Re: BUG #5307: Crash in AllocSetAlloc

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Igor Lasic" <igor(at)a-bb(dot)net>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5307: Crash in AllocSetAlloc
Date: 2010-02-02 19:31:25
Message-ID: 29091.1265139085@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Igor Lasic" <igor(at)a-bb(dot)net> writes:
> We have an application running C-API stored procedures. After running for a
> while postgres crashes with:

> If I increase shared memory application runs longer but eventually crashes.

The odds are incredibly high that this means there's a memory-stomping
bug in your C stored procedures. You might try testing them in a build
with --enable-debug + --enable-cassert, which will enable some sanity
checking code in the memory context support.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Kelly SACAULT 2010-02-02 20:11:04 BUG #5308: How to disable Case sensitivity on naming identifiers
Previous Message Alvaro Herrera 2010-02-02 19:13:43 Re: BUG #5307: Crash in AllocSetAlloc