| From: | Sushant Sinha <sushant354(at)gmail(dot)com> |
|---|---|
| To: | Jan Urbański <wulczer(at)wulczer(dot)org> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: PL/Python: No stack trace for an exception |
| Date: | 2011-07-21 13:48:27 |
| Message-ID: | 1311256107.2302.5.camel@dragflick |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 2011-07-21 at 15:31 +0200, Jan Urbański wrote:
> On 21/07/11 15:27, Sushant Sinha wrote:
> > I am using plpythonu on postgres 9.0.2. One of my python functions was
> > throwing a TypeError exception. However, I only see the exception in the
> > database and not the stack trace. It becomes difficult to debug if the
> > stack trace is absent in Python.
> >
> > logdb=# select get_words(forminput) from fi;
> > ERROR: PL/Python: TypeError: an integer is required
> > CONTEXT: PL/Python function "get_words"
> >
> > And here is the error if I run that function on the same data in python:
> >
> > [traceback]
> >
> > Is this a known problem or this needs addressing?
>
> Yes, traceback support in PL/Python has already been implemented and is
> a new feature that will be available in PostgreSQL 9.1.
>
> Cheers,
> Jan
Thanks Jan! Just one more reason to try 9.1.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-07-21 15:51:14 | Re: Single pass vacuum - take 1 |
| Previous Message | Peter Geoghegan | 2011-07-21 13:34:34 | Re: PL/Python: No stack trace for an exception |