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

Re: plpython improvements

From: Sven <sven(at)spam(dot)pri(dot)ee>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Hannu Krosing <hannu(at)tm(dot)ee>, Marko Kreen <markokr(at)gmail(dot)com>,Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-patches(at)postgresql(dot)org
Subject: Re: plpython improvements
Date: 2006-06-17 06:05:15
Message-ID: 1150524315.44939b9be413b@webmail.elion.ee (view raw or flat)
Thread:
Lists: pgsql-patches
Quoting Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>:

> 
> Added to TODO:
> 
>            o Allow PL/python to composite types and result sets
>              once buggy assert-enabled versions of python can be
detected

I actually tried to work other way around -- get all known buggy systems
fixed:
1) Debugging Python version: bug acknowledged, v2.5 fixed, v2.4 waiting
(http://sourceforge.net/tracker/index.php?func=detail&aid=1483133&group_id=5470&atid=105470)
2) Fedora: >=v5 fixed, will be backported to version 4 also
(https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=192592)

If this approach is not satisfactionary and assertion predetection is
still requested, only solution I see is to catch signal SIGABRT, set
flag, longjmp back and report error.
But I really don't like it.


-- 
Sven Suursoho

In response to

Responses

pgsql-patches by date

Next:From: Tom LaneDate: 2006-06-17 15:47:46
Subject: Re: plpython improvements
Previous:From: Tom LaneDate: 2006-06-17 00:26:19
Subject: Re: table/index fillfactor control, try 2

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