From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Ian Harding" <ianh(at)tpchd(dot)org> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Core Dump |
Date: | 2002-10-01 21:08:06 |
Message-ID: | 17046.1033506486@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Ian Harding" <ianh(at)tpchd(dot)org> writes:
> I hacked my pltcl.so the other day, but all has been well up to now.
> I added a few SPI_freetuptable() to keep pltcl from hogging all the
> memory. I wonder if I hacked it a little wrong.
Looks that way. The stack trace doesn't seem completely trustworthy,
though, so you might want to consider recompiling with --enable-debug.
Note that you seem to be inside a re-entrant use of pltcl (outer
function is triggering a trigger also written in pltcl). I'm wondering
if your tuptable hacking is not taking account of the possibility of
re-entrancy. This might be a bug that had been latent in pltcl all
along, and was only exposed when you tried to free stuff ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2002-10-01 21:44:05 | Re: [pgsql-performance] Deletes from tables with foreign keys taking too long |
Previous Message | Philip Hallstrom | 2002-10-01 21:03:00 | Re: Design Tools |