For debugging PL/Python functions, I'm often tempted to write something
like

rv = plpy.execute(...)
plpy.info(rv)

which prints something unhelpful like

<PLyResult object at 0xb461d8d8>

By implementing a "str" handler for the result object, it now prints
something like

<PLyResult status=5 nrows=2 rows=[{'foo': 1, 'bar': '11'}, {'foo': 2, 'bar': '22'}]>

Patch attached for review.

Responses

• Re: PL/Python result object str handler at 2013-01-08 09:32:40 from Magnus Hagander
• Re: PL/Python result object str handler at 2013-02-02 20:43:24 from Steve Singer

pgsql-hackers by date

Next:	From: Peter Eisentraut	Date: 2013-01-08 03:12:22
	Subject: Re: bad examples in pg_dump README
Previous:	From: Noah Misch	Date: 2013-01-08 02:49:57
	Subject: lazy_vacuum_heap()'s removal of HEAPTUPLE_DEAD tuples