pproach 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
---(end of broadcast)---
TIP 3:
1) named parameters additionally to args[]
2) return composite-types from plpython as dictionary
3) return result-set from plpython as list, iterator or generator
Test script attached (patch-test.sql) but not integrated to plpython
test-suite.
--
Sven Suursoho
patch-test.sql
Description
on a
> version against CVS HEAD?
Attached patch for CVS HEAD.
Testscripts remained same (obviously :) but still not integrated.
--
Sven SuursohoIndex: plpython.c
===
RCS file: /projects/cvsroot/pgsql/src/pl/plpython/plpython.c,v
ssive assert.
See
http://mail.python.org/pipermail/python-checkins/2005-August/046571.html.
I guess there should be warning somewhere as Hannu said but didn't know
where to put it.
--
Sven SuursohoIndex: plpython.c
===
RCS file:
Sun, 30 Apr 2006 19:14:28 +0300, Tom Lane <[EMAIL PROTECTED]>:
"Sven Suursoho" <[EMAIL PROTECTED]> writes:
Unfortunately, there is still one problem when using unpatched python,
caused by too aggressive assert.
See
http://mail.python.org/pipermail/python-checkins/2005
Sun, 30 Apr 2006 20:48:48 +0300, Bruce Momjian :
Sun, 30 Apr 2006 19:14:28 +0300, Tom Lane <[EMAIL PROTECTED]>:
> "Sven Suursoho" <[EMAIL PROTECTED]> writes:
>> Unfortunately, there is still one problem when using unpatched
python,
>> cause
Sun, 30 Apr 2006 21:43:03 +0300, Tom Lane <[EMAIL PROTECTED]>:
"Sven Suursoho" <[EMAIL PROTECTED]> writes:
So, what about this in configure:
if --with-python && test_iterator_app_crashes
# errcode(FEATURE_NOT_SUPPORTED), errmsg(patch your python)
disable_it
Hi,
Sun, 30 Apr 2006 19:14:28 +0300, Tom Lane <[EMAIL PROTECTED]>:
"Sven Suursoho" <[EMAIL PROTECTED]> writes:
Unfortunately, there is still one problem when using unpatched python,
caused by too aggressive assert.
http://mail.python.org/pipermail/python-checkins/2005-A
uggy gethostbyname(). Fact, that we know about this,
shouldn't stop us developing TCP/IP applications. Especially, if there is
also patch for this bug :)
It would be real shame to prevent using generator for SETOF functions
because it is most natural match for plpgsql'
mapping protocol. Currently only dict as previously, though. But still,
ready for new fancy unforeseen Python features without recompiling PG.
Additionally, now it is possible to return compose types as Python tuples.
Will create patch whenever final decision is made about generators.
--
Sven
Sun, 07 May 2006 12:36:59 +0300, Sven Suursoho <[EMAIL PROTECTED]>:
Btw, we developed returning compose types further. Basically did same as
for SETOF functions -- allow to return any Python object that conforms
to mapping protocol. Currently only dict as previously, though. But
I'm not so good with rpm packaging
system, just looked output of compilation stage.
So, we are back on square one...
--
Sven Suursoho
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
ect this patch on
security grounds.
Here it is, updated against CVS HEAD.
Will create documentation after acceptance of patch.
--
Sven SuursohoIndex: plpython.c
===
RCS file: /projects/cvsroot/pgsql/src/pl/plpython/plpython.c,v
retrie
hly as I'm not native English
speaker nor didn't manage to generate documentation from SGML sources (
openjade:postgres.sgml:3:55:W: cannot generate system identifier for public
text "-//OASIS//DTD DocBook V4.2//EN")
--
Sven Suursoho
plpython-patch.tar.gz
De
14 matches
Mail list logo
