From: | "Sven Suursoho" <sven(at)spam(dot)pri(dot)ee> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: plpython improvements |
Date: | 2006-04-30 16:34:22 |
Message-ID: | op.s8txnkzgplgmb3@localhost |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Sun, 30 Apr 2006 19:14:28 +0300, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> "Sven Suursoho" <sven(at)spam(dot)pri(dot)ee> 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-August/046571.html.
>> I guess there should be warning somewhere as Hannu said but didn't know
>> where to put it.
>
> I don't think we are going to be able to accept a patch that causes the
> server to crash when using any but a bleeding-edge copy of Python.
Actually normal python installations do not cause problem, only debugging
versions do.
Anyway, if you think that this doesn't count as an argument, there is
nothing that we can do from PG-side except drop returning SETOF as
iterator/generator and only allow return SETOF as list.
--
Sven Suursoho
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2006-04-30 17:48:48 | Re: plpython improvements |
Previous Message | Tom Lane | 2006-04-30 16:14:28 | Re: plpython improvements |