Re: PlPython

From: Hannu Krosing <hannu(at)tm(dot)ee>
To: Gerhard Häring <gh(at)ghaering(dot)de>
Cc: Kevin Jacobs <jacobs(at)penguin(dot)theopalgroup(dot)com>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: PlPython
Date: 2003-06-30 07:48:02
Message-ID: 1056959282.6907.8.camel@fuji.krosing.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Gerhard Häring kirjutas E, 30.06.2003 kell 07:39:
> Hannu Krosing wrote:

> > IIRC python 1.5.2 has a perfectly good RExec.
>
> You are likely mistaken. Because I was interested in getting this
> problem solved for plpython and because most rexec problems are because
> of the new-style classes in Python 2.2 and later, I asked on
> comp.lang.python wether it was safe with 2.1 and earlier.
>
> Martin von Löwis told me it probably wasn't in
> http://groups.google.com/groups?selm=m3y8ztib79.fsf%40mira.informatik.hu-berlin.de

Uups! I got that impression from the emails which claimed that new-style
classes make it near impossilble to fix.

> > Or is there a requirement that only latest language versions are used in
> > pg 74 ;)
>
> No, but I find it hard to believe that PL/python is used by untrusted
> users at all, so making it untrusted might not really be a problem in
> real life.

That is most likely true.

And trusted users like to use untrusted languages, so they can send
email, get xml via http and write files ;)

-------------
Hannu

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Csaba Nagy 2003-06-30 08:45:41 Re: Making pgsql error messages more developers' friendly.
Previous Message Hannu Krosing 2003-06-30 07:30:47 Re: [HACKERS] PlPython

Browse pgsql-hackers by date

  From Date Subject
Next Message Carlos Guzman Alvarez 2003-06-30 10:02:20 Re: Question about array read using protocol 3.0 implementation
Previous Message Hannu Krosing 2003-06-30 07:30:47 Re: [HACKERS] PlPython