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.
Showing
- doc/src/sgml/spi.sgml 3 additions, 3 deletionsdoc/src/sgml/spi.sgml
- src/backend/executor/spi.c 57 additions, 43 deletionssrc/backend/executor/spi.c
- src/backend/tcop/dest.c 2 additions, 2 deletionssrc/backend/tcop/dest.c
- src/include/access/printtup.h 4 additions, 2 deletionssrc/include/access/printtup.h
- src/pl/plpgsql/src/pl_exec.c 39 additions, 13 deletionssrc/pl/plpgsql/src/pl_exec.c
Loading
Please register or sign in to comment