Re: plpython improvements - Mailing list pgsql-patches

From Bruce Momjian
Subject Re: plpython improvements
Date
Msg-id 200604301748.k3UHmmX15023@candle.pha.pa.us
Whole thread Raw
In response to Re: plpython improvements  ("Sven Suursoho" <sven@spam.pri.ee>)
Responses Re: plpython improvements  ("Sven Suursoho" <sven@spam.pri.ee>)
List pgsql-patches
Sven Suursoho wrote:
> Sun, 30 Apr 2006 19:14:28 +0300, Tom Lane <tgl@sss.pgh.pa.us>:
>
> > "Sven Suursoho" <sven@spam.pri.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.

Can't we detect a debug build and disable the feature?

--
  Bruce Momjian   http://candle.pha.pa.us
  EnterpriseDB    http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

pgsql-patches by date:

Previous
From: "Sven Suursoho"
Date:
Subject: Re: plpython improvements
Next
From: "Sven Suursoho"
Date:
Subject: Re: plpython improvements