Skip site navigation (1) Skip section navigation (2)

Re: can't load plpython

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Euler Taveira de Oliveira <euler(at)timbira(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: can't load plpython
Date: 2009-03-31 17:14:20
Message-ID: 20090331171420.GY23023@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-hackers
Euler Taveira de Oliveira wrote:
> Tom Lane escreveu:
> > Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> >> ... However, on HEAD this is crashing for me, and it's right when plpython
> >> loads.  Backtrace below.
> > 
> > Does plpython pass its regression tests for you (I'd suppose not)?
> > 
> > For me on Fedora 10 x86_64, CVS HEAD plus python 2.5.2 passes regression
> > but the given example still dumps core.  postmaster log says
> > 
> > postgres: tgl regression [local] SELECT: Objects/stringobject.c:107: PyString_FromString: Assertion `str != ((void *)0)' failed.
> > LOG:  server process (PID 4714) was terminated by signal 6: Aborted
> > LOG:  terminating any other active server processes
> > 
> PyString_FromString() [1] fails to return something useful, i.e, null pointer
> when  its argument is null.  The trivial fix (that is attached) is to ensure
> that we don't pass a null pointer as the second argument of
> PyDict_SetItemString(). Of course, it's a Python bug and I filled it [3].

I'm not sure I'm reading this right, but isn't this preventing a
plpytHon function to work if parameters don't have names assigned?
i.e. apparently I can't just use args[0].  I'm sure I'm wrong on this ...?

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

pgsql-hackers by date

Next:From: Josh BerkusDate: 2009-03-31 17:16:49
Subject: Re: Partitioning feature ...
Previous:From: Tom LaneDate: 2009-03-31 17:10:56
Subject: Re: Solaris getopt_long and PostgreSQL

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group