Re: PlPython

From: elein <elein(at)varlena(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Kevin Jacobs <jacobs(at)penguin(dot)theopalgroup(dot)com>, joconnor(at)cybermesa(dot)com, pgsql-general(at)postgresql(dot)org
Subject: Re: PlPython
Date: 2003-06-30 21:14:09
Message-ID: 200306301414.09929.elein@varlena.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers


That the imports "work" means that you *can*
import them. That does not mean I tested
their functionality (except for string).

elein

On Monday 30 June 2003 14:11, elein wrote:
> OK. SD and GD behaviours are valid as stated in the
> original docs. I assume, therefore, that TD (for triggers)
> also behaves.
>
> All of the "forbidded" imports work with the following
> exceptions:
> * mpz -- undefined symbol -- probably just my system
> * some modules are dependent on others so
> you may have to order them correctly. This is
> just I python thing I think.
>
> I was testing on SuSe 7.3 with Kevin's patch applied to
> PostgreSQL v7.3.2.
>
> Sorry about the mixup earlier. But the "forbidden"
> modules part still needs to be tossed for the new
> doc.
>
> elein
>
> On Monday 30 June 2003 13:58, elein wrote:
> > (@***(at)*#$*(@#&&)
> >
> > Checking on the build that was supposed to install
> > the patch, I now see I have an incorrect conf argument.
> > Take 2. I'll rerun these tests right now with a good build.
> > Give me 1/2 hour max.
> >
> > --elein
> >
> >
> > On Monday 30 June 2003 13:45, Tom Lane wrote:
> > > elein <elein(at)varlena(dot)com> writes:
> > > > According to my testing that statement about dictionaries
> > > > is still valid.
> > >
> > > What are you testing? It sure looks like it's not the untrusted version
> > > of plpython:
> > >
> > > > ERROR: plpython: Call of function `__plpython_procedure_import_test_1849240' failed.
> > > > exceptions.SystemError: Failed to load the builtin codecs: untrusted dynamic module: _codecs
> > >
> > > AFAIK that "untrusted dynamic module" error is from RExec.
> > >
> > > regards, tom lane
> > >
> > > ---------------------------(end of broadcast)---------------------------
> > > TIP 6: Have you searched our list archives?
> > >
> > > http://archives.postgresql.org
> > >
> > >
> >
> > --
> > =============================================================
> > elein(at)varlena(dot)com Database Consulting www.varlena.com
> > PostgreSQL General Bits http:/www.varlena.com/GeneralBits/
> > "Free your mind the rest will follow" -- en vogue
> >
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 4: Don't 'kill -9' the postmaster
> >
> >
>
> --
> =============================================================
> elein(at)varlena(dot)com Database Consulting www.varlena.com
> PostgreSQL General Bits http:/www.varlena.com/GeneralBits/
> "Free your mind the rest will follow" -- en vogue
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html
>
>

--
=============================================================
elein(at)varlena(dot)com Database Consulting www.varlena.com
PostgreSQL General Bits http:/www.varlena.com/GeneralBits/
"Free your mind the rest will follow" -- en vogue

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2003-06-30 21:32:18 Re: PlPython
Previous Message elein 2003-06-30 21:11:57 Re: PlPython

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-06-30 21:27:38 Re: [HACKERS] Missing array support
Previous Message elein 2003-06-30 21:11:57 Re: PlPython