Re: PLPGSQL bug in implicit SELECT

Kovacs Zoltan <kovacsz(at)pc10(dot)radnoti-szeged(dot)sulinet(dot)hu> writes:
> Unfortunately I'm getting
> testdb=# select testfunc();
> ERROR: query "SELECT column1 FROM table WHERE column2 LIKE '%anything%'
> ORDER BY column3 LIMIT 1" returned more than one column

This appears fixed in current sources. I believe the relevant bugfix is:

2001-05-27 16:48 tgl

* src/: backend/executor/execJunk.c, backend/executor/execMain.c,
include/executor/executor.h, include/nodes/execnodes.h: When using
a junkfilter, the output tuple should NOT be stored back into the
same tuple slot that the raw tuple came from, because that slot has
the wrong tuple descriptor. Store it into its own slot with the
correct descriptor, instead. This repairs problems with SPI
functions seeing inappropriate tuple descriptors --- for example,
plpgsql code failing to cope with SELECT FOR UPDATE.

regards, tom lane