From: | tgl(at)postgresql(dot)org (Tom Lane) |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql-server/ oc/src/sgml/Tag: oc/src/sgml/REL ... |
Date: | 2003-01-21 22:06:36 |
Message-ID: | 20030121220636.82469476585@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
CVSROOT: /cvsroot
Module name: pgsql-server
Changes by: tgl(at)postgresql(dot)org 03/01/21 17:06:36
Modified files:
doc/src/sgml : Tag: REL7_3_STABLE spi.sgml
src/backend/executor: Tag: REL7_3_STABLE spi.c
src/backend/tcop: Tag: REL7_3_STABLE dest.c
src/include/access: Tag: REL7_3_STABLE printtup.h
src/pl/plpgsql/src: Tag: REL7_3_STABLE pl_exec.c
Log message:
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-01-22 00:07:01 | pgsql-server/src/backend/optimizer plan/create ... |
Previous Message | Tom Lane | 2003-01-21 22:06:12 | pgsql-server/ oc/src/sgml/spi.sgml rc/backend/ ... |