Re: Plpython crashing the backend in one easy step - fix - Mailing list pgsql-hackers

From Bradley McLean
Subject Re: Plpython crashing the backend in one easy step - fix
Date
Msg-id 20011116150001.A2410@bradm.net
Whole thread Raw
In response to Re: Plpython crashing the backend in one easy step - fix  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Plpython crashing the backend in one easy step - fix
List pgsql-hackers
* Kevin Jacobs (jacobs@penguin.theopalgroup.com) [011116 13:15]:
> On Fri, 16 Nov 2001, Tom Lane wrote:
> > --- feature.expected    Fri May 25 11:48:33 2001
> > +++ feature.output    Fri Nov 16 13:00:15 2001
> > @@ -29,7 +29,7 @@
> >  (1 row)
> >
> >  SELECT import_fail();
> > -NOTICE:  ('import socket failed -- untrusted dynamic module: _socket',)
> > +NOTICE:  ('import socket failed -- untrusted dynamic module: socket',)
> >      import_fail
> >  --------------------
> >   failed as expected
> >
> > I assume you guys both get the "expected" output?  Perhaps this should
> > be noted as a possible platform discrepancy.
> 
> This diff is most likely a platform issue where the module printed can
> change depending on the version of Python installed.  Its annoying, but
> harmless.

I can confirm that:  It occurs on stock python 1.5.2 (default on even the
latest RH 7.2 linux).  Betweeen 1.5 and 2.0 the low level code was moved
from socket to _socket to make it possible to include a high level python
wrapper called socket.

I've reviewed the merge from CVS and it appears correct.  Thanks!

-Brad


pgsql-hackers by date:

Previous
From: matthew@zeut.net
Date:
Subject: Re: Super Optimizing Postgres
Next
From: Tom Lane
Date:
Subject: Re: Plpython crashing the backend in one easy step - fix