From: | heikki(at)postgresql(dot)org (Heikki Linnakangas) |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Add new SPI_OK_REWRITTEN return code to SPI_execute and friends, |
Date: | 2009-01-21 11:02:41 |
Message-ID: | 20090121110241.0C92B7559ED@cvs.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Log Message:
-----------
Add new SPI_OK_REWRITTEN return code to SPI_execute and friends, for the
case that the command is rewritten into another type of command. The old
behavior to return the command tag of the last executed command was
pretty surprising. In PL/pgSQL, for example, it meant that if a command
was rewritten to a utility statement, FOUND wasn't set at all.
Modified Files:
--------------
pgsql/doc/src/sgml:
spi.sgml (r1.63 -> r1.64)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/spi.sgml?r1=1.63&r2=1.64)
pgsql/src/backend/executor:
spi.c (r1.206 -> r1.207)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/spi.c?r1=1.206&r2=1.207)
pgsql/src/include/executor:
spi.h (r1.70 -> r1.71)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/executor/spi.h?r1=1.70&r2=1.71)
pgsql/src/pl/plpgsql/src:
pl_exec.c (r1.229 -> r1.230)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpgsql/src/pl_exec.c?r1=1.229&r2=1.230)
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2009-01-21 11:13:15 | pgsql: Forgot to handle the new SPI_OK_REWRITTEN result code in a couple |
Previous Message | Magnus Hagander | 2009-01-21 10:30:02 | pgsql: Make win32 builds always do SetEnvironmentVariable() when doing |