The following bug has been logged online:

Bug reference: 2791
Logged by: Raman Dabhade
Email address: raman.dabhade (AT) coalitiondev (DOT) com
PostgreSQL version: 8.1
Operating system: Win XP
Description: Error while commiting
Details:

ERROR: SPI_execute_plan failed executing query "commit":
SPI_ERROR_TRANSACTION
CONTEXT: PL/pgSQL function "processrecords" line 4 at SQL statement

When executing following procedure:

CREATE OR REPLACE FUNCTION processRecords()
RETURNS int8 AS
$BODY$
declare
begin

commit ;

return 0;
end;
$BODY$
LANGUAGE 'plpgsql' VOLATILE;

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

On Tue, Nov 28, 2006 at 02:13:15PM +0000, Raman Dabhade wrote:
http://www.postgresql.org/docs/8.1/i...structure.html

"Functions and trigger procedures are always executed within a
transaction established by an outer query -- they cannot start or
commit that transaction, since there would be no context for them
to execute in."

--
Michael Fuhr

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