From: Gerhard Häring <lists@ghaering.de>
To: pgsql-interfaces@postgresql.org
Subject: Re: PL/Python import _sre module error
Date: Mon, 16 Jun 2003 22:39:53 +0200
Message-ID: <3EEE2B19.5070007@ghaering.de> (raw)
In-Reply-To: <1055795688.1529.19.camel@gwpogo.localdomain>
References: <000a01c331d8$edd28680$0df4623e@79>
<200306161357.20600.JLT@WVInter.Net>
<1055795688.1529.19.camel@gwpogo.localdomain>
Glenn R Williams wrote:
> Hi All,
>
> Does anyone else have a problem with importing the re package
> I am using:
>
> Redhat 9.0
> PostgreSQL 7.3.3
> Python 2.2.2.26
>
> When I create a function:
>
> import re
> o = args[0]
> b = re.match(r"^t.*",o)
> if b:
> return "fits the bill"
> return "failed the test"
>
> PostgreSQL fails, and returns the error message:
>
> exceptions.ImportError: No module named _sre
>
> If I go into python, this is not a problem, so I suppose it is somehow
> due to the restricted execution environment and/or PostgreSQL. But
> that's as far as I get.
Correct. re is not enabled, because you can create arbitrary cpu (and
perhaps also memory) utilization with it. Thus it's unsafe.
> Any suggestions on how to pinpoint the problem? [...]
Fork pl/python and create an unsafe version without any restrictions?
That's what I once did just for fun. I think that'll be necessary
anyway, because with Python >= 2.2.3, rexec and friends are disabled anyway.
-- Gerhard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: lists@ghaering.de
Subject: Re: PL/Python import _sre module error
In-Reply-To: <3EEE2B19.5070007@ghaering.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox