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

Re: BUG #5835: PL/Python crashes

From: "Julien Demoor" <jdemoor(at)gmail(dot)com>
To: <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #5835: PL/Python crashes
Date: 2011-01-16 12:55:43
Message-ID: 001301cbb57c$b018ab50$104a01f0$@com (view raw or flat)
Thread:
Lists: pgsql-bugs
I just tried and it works. Thank you very much.

-----Message d'origine-----
De : Alex Hunsaker [mailto:badalex(at)gmail(dot)com] 
Envoyé : vendredi 14 janvier 2011 07:33
À : Julien Demoor
Cc : pgsql-bugs(at)postgresql(dot)org
Objet : Re: [BUGS] BUG #5835: PL/Python crashes

On Thu, Jan 13, 2011 at 06:57, Julien Demoor <jdemoor(at)gmail(dot)com> wrote:
>
> The following bug has been logged online:
>
> Bug reference:      5835
> Logged by:          Julien Demoor
> Email address:      jdemoor(at)gmail(dot)com
> PostgreSQL version: 9.0.2
> Operating system:   Ubuntu Linux
> Description:        PL/Python crashes
> Details:

> BEGIN;
> CREATE OR REPLACE FUNCTION test_none_3(a numeric[]) RETURNS 
> numeric(12,4) AS $$
>    return 1;
> $$ LANGUAGE plpython2u;
> SELECT test_none_3('{NULL, NULL, NULL}'::numeric[]) FROM
> generate_series(1,244) ORDER BY generate_series DESC LIMIT 1; 
> ROLLBACK;

It looks like we are not incrementing a reference count for NULL entries in an array.  The attached fixes it for me.  I did look for other places where we might have missed this and did not find any.  ( the PyDict_SetItemString() that use Py_None look fishy, but apparently work ).

Can you see if it fixes it for you?


In response to

pgsql-bugs by date

Next:From: Denish PatelDate: 2011-01-16 16:06:42
Subject: Re: date_trunc check constraint causes errors when restoring in a db with a different time zone
Previous:From: Tim UckunDate: 2011-01-15 20:43:11
Subject: Re: Problems with adding a is not null to a query.

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