BUG #2836: SPI_execute_plan failed on pl/pgsql function that worked on 8.1

From: "Albert Cervera i Areny" <albert(at)sedifa(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #2836: SPI_execute_plan failed on pl/pgsql function that worked on 8.1
Date: 2006-12-18 09:49:29
Message-ID: 200612180949.kBI9nTiH093018@wwwmaster.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


The following bug has been logged online:

Bug reference: 2836
Logged by: Albert Cervera i Areny
Email address: albert(at)sedifa(dot)com
PostgreSQL version: 8.2
Operating system: Debian GNU/Linux
Description: SPI_execute_plan failed on pl/pgsql function that worked
on 8.1
Details:

I get the following error on a function that worked correctly on 8.1:

ERROR: SPI_execute_plan failed executing query "UPDATE
pg_catalog.pg_settings SET setting= $1 WHERE name='search_path'":
Unrecognized SPI code 0
CONTEXT: PL/pgSQL function "ventas_por_grupo_conjunta_tmp" line 23 at SQL
statement
SQL function "ventas_por_grupo_conjunta" statement 1

The function tries to reestablish the search_path with the following UPDATE
command:

$body$
SELECT setting INTO path FROM pg_catalog.pg_settings WHERE
name='search_path';

...here the rest of the function...

UPDATE pg_catalog.pg_settings SET setting=path WHERE name='search_path
$body$

I've been able to work around this by using:

EXECUTE 'UPDATE pg_catalog.pg_settings SET setting=''' || path || ''' WHERE
name=''search_path''';

instead.

Hope this helps in finding out the problem. I don't think the behaviour is
intended.

Please, contact if you want me to test any patches.

Thanks!

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message canli 2006-12-18 10:00:07 BUG #2837: i received ERROR: failed to build any 7-way joins
Previous Message William ZHANG 2006-12-18 08:17:54 BUG #2835: Table inheritance and statement level trigger.