diff options
| -rw-r--r-- | src/pl/plpgsql/src/pl_exec.c | 16 |
1 files changed, 10 insertions, 6 deletions
diff --git a/src/pl/plpgsql/src/pl_exec.c b/src/pl/plpgsql/src/pl_exec.c index 6096eb9e100..0599f1de8aa 100644 --- a/src/pl/plpgsql/src/pl_exec.c +++ b/src/pl/plpgsql/src/pl_exec.c @@ -8,7 +8,7 @@ * * * IDENTIFICATION - * $PostgreSQL: pgsql/src/pl/plpgsql/src/pl_exec.c,v 1.180.2.7 2009/01/07 20:39:15 tgl Exp $ + * $PostgreSQL: pgsql/src/pl/plpgsql/src/pl_exec.c,v 1.180.2.8 2009/01/14 09:53:57 heikki Exp $ * *------------------------------------------------------------------------- */ @@ -2425,13 +2425,19 @@ exec_stmt_execsql(PLpgSQL_execstate *estate, /* * Check for error, and set FOUND if appropriate (for historical reasons - * we set FOUND only for certain query types). Also Assert that we - * identified the statement type the same as SPI did. + * we set FOUND only for certain query types). + * + * Note: the command type indicated by return code might not match + * mod_stmt, if there is an INSTEAD OF rule rewriting an UPDATE into an + * INSERT, for example. In that case, the INSERT doesn't have canSetTag + * set, mod_stmt is false, and SPI_execute_plan sets SPI_processed to + * zero. We'll set FOUND to false here in that case. If the statement is + * rewritten into a utility statement, however, FOUND is left unchanged. + * Arguably that's a bug, but changing it now could break applications. */ switch (rc) { case SPI_OK_SELECT: - Assert(!stmt->mod_stmt); exec_set_found(estate, (SPI_processed != 0)); break; @@ -2441,13 +2447,11 @@ exec_stmt_execsql(PLpgSQL_execstate *estate, case SPI_OK_INSERT_RETURNING: case SPI_OK_UPDATE_RETURNING: case SPI_OK_DELETE_RETURNING: - Assert(stmt->mod_stmt); exec_set_found(estate, (SPI_processed != 0)); break; case SPI_OK_SELINTO: case SPI_OK_UTILITY: - Assert(!stmt->mod_stmt); break; default: |