Re: [PATCHES] plpython improvements

From: Michael Fuhr <mike(at)fuhr(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org, Sven Suursoho <pg(at)spam(dot)pri(dot)ee>
Subject: Re: [PATCHES] plpython improvements
Date: 2006-08-18 21:17:14
Message-ID: 20060818211714.GA85419@winnie.fuhr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On Fri, Aug 18, 2006 at 04:27:23PM -0400, Tom Lane wrote:
> Anyone in a position to review the pending plpython patch?
> http://archives.postgresql.org/pgsql-patches/2006-08/msg00151.php

In several places the code does this:

so = PyObject_Str(value);
valuestr = PyString_AsString(so);

We've previously learned that calling PyString_AsString() without
checking the return value of PyObject_Str() can result in a
segmentation fault.

http://archives.postgresql.org/pgsql-committers/2005-07/msg00233.php

I haven't examined the current patch closely enough to know whether
PyObject_Str() can possibly return NULL, but several occurrences
of the above code snippet caught my eye because we had dealt with
it before.

--
Michael Fuhr

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message andrew 2006-08-18 22:27:23 Re: [PATCHES] plpython improvements
Previous Message Josh Berkus 2006-08-18 20:38:26 Re: BugTracker (Was: Re: 8.2 features status)

Browse pgsql-patches by date

  From Date Subject
Next Message andrew 2006-08-18 22:27:23 Re: [PATCHES] plpython improvements
Previous Message Tom Lane 2006-08-18 20:27:23 Re: [PATCHES] plpython improvements