Tom Lane wrote:
> Alvaro Herrera <alvherre@commandprompt.com> writes:
> > It works for me now. Thanks to Euler for tracking the Python problem
> > down and to you for the commit!
>
> Hmph. I wonder what caused that crash you reported originally? The
> backtrace doesn't look like it's explained by the argument-name bug:
> http://archives.postgresql.org/pgsql-hackers/2009-03/msg01344.php
>
> Maybe that backtrace is just bogus, though --- if you'd pointed gdb
> at the wrong executable version, or something, you could have come
> up with silly results.
No, the backtrace is right -- I get the same if I revert the plpython.c
commit. I have no idea why the backtrace looks like this. It's even
compiled with -O0.
> Anyway, if it's no longer reproducible, we probably shouldn't spend
> too much time on it.
Okay.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support