From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Jean-Baptiste Quenot <jbq(at)caraldi(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Bug in plpython's Python Generators |
Date: | 2010-10-21 18:48:57 |
Message-ID: | 1287686694-sup-8959@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Excerpts from Alvaro Herrera's message of jue oct 21 15:32:53 -0300 2010:
> Excerpts from Jean-Baptiste Quenot's message of jue oct 21 09:20:16 -0300 2010:
>
> > I get this error when calling the function:
> >
> > test=# select foobar();
> > ERROR: error fetching next item from iterator
>
> I can reproduce this here. The first bug to solve is, I think, getting
> a more meaningful error report.
Something like this. Somebody that really knows their way around Python
has to clean this up.
alvherre=# select * from foobar();
ERROR: error extrayendo el próximo elemento del iterador
CONTEXTO: falló SPI_execute: SPI_ERROR_UNCONNECTED
función PL/Python «foobar»
I think all error cases in plpython need some improvement so that they
show the error message from Python. Right now they are ignored.
... and presumably somebody can fix the real bug that Jean-Baptiste hit,
too.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Attachment | Content-Type | Size |
---|---|---|
plpy.patch | application/octet-stream | 908 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Cédric Villemain | 2010-10-21 19:01:30 | Re: Exposing an installation's default value of unix_socket_directory |
Previous Message | Peter Eisentraut | 2010-10-21 18:44:36 | Re: Per-column collation, work in progress |