]> granicus.if.org Git - postgresql/commit
Fix coredump problem in plpgsql's RETURN NEXT. When a SELECT INTO
authorTom Lane <tgl@sss.pgh.pa.us>
Tue, 21 Jan 2003 22:06:12 +0000 (22:06 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Tue, 21 Jan 2003 22:06:12 +0000 (22:06 +0000)
commita4482f4c4c4e052f954f4f333ae8f5ce999613ab
treef677db02aeb6836cb9eb23f0f8aa679e39c27b2b
parentf8d8266ac5717296ac380123e8907a3098d457ef
Fix coredump problem in plpgsql's RETURN NEXT.  When a SELECT INTO
that's selecting into a RECORD variable returns zero rows, make it
assign an all-nulls row to the RECORD; this is consistent with what
happens when the SELECT INTO target is not a RECORD.  In support of
this, tweak the SPI code so that a valid tuple descriptor is returned
even when a SPI select returns no rows.
doc/src/sgml/spi.sgml
src/backend/executor/spi.c
src/backend/tcop/dest.c
src/include/access/printtup.h
src/pl/plpgsql/src/pl_exec.c