Log Message:
-----------
Fix plperl and pltcl error handling per my previous proposal. SPI
operations are now run as subtransactions, so that errors in them
can be reported as ordinary Perl or Tcl errors and caught by the
normal error handling convention of those languages. Also do some
minor code cleanup in pltcl.c: extract a large chunk of duplicated
code in pltcl_SPI_execute and pltcl_SPI_execute_plan into a shared
subroutine.

Modified Files:
--------------
pgsql/doc/src/sgml:
plperl.sgml (r2.31 -> r2.32)
(http://developer.postgresql.org/cvsw...1=2.31&r2=2.32)
pltcl.sgml (r2.31 -> r2.32)
(http://developer.postgresql.org/cvsw...1=2.31&r2=2.32)
release.sgml (r1.309 -> r1.310)
(http://developer.postgresql.org/cvsw...1.309&r2=1.310)
pgsql/src/pl/plperl:
plperl.c (r1.59 -> r1.60)
(http://developer.postgresql.org/cvsw...1=1.59&r2=1.60)
pgsql/src/pl/tcl:
pltcl.c (r1.93 -> r1.94)
(http://developer.postgresql.org/cvsw...1=1.93&r2=1.94)
pgsql/src/pl/tcl/test:
runtest (r1.4 -> r1.5)
(http://developer.postgresql.org/cvsw...?r1=1.4&r2=1.5)
test_queries.sql (r1.3 -> r1.4)
(http://developer.postgresql.org/cvsw...?r1=1.3&r2=1.4)
test_setup.sql (r1.6 -> r1.7)
(http://developer.postgresql.org/cvsw...?r1=1.6&r2=1.7)

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match