NotificationsYou must be signed in to change notification settings
Fork6
Star31

Commit7bdf9b8

committed

Fix GET DIAGNOSTICS for case of assignment to function's first variable.

An incorrect and entirely unnecessary "safety check" in exec_stmt_getdiag()caused the code to treat an assignment to a variable with dno zero as ano-op. Unfortunately, that's a perfectly valid dno. This has been brokensince GET DIAGNOSTICS was invented. It's not terribly surprising that thebug went unnoticed for so long, since in most cases you probably wouldn'tuse the function's first-created variable (normally its first parameter)as a GET DIAGNOSTICS target. Nonetheless, it's broken. Per bug #6551from Adam Buraczewski.

1 parent3bf25a2 commit7bdf9b8Copy full SHA for 7bdf9b8

File tree

1 file changed

-9

lines changed

src/pl/plpgsql/src
- pl_exec.c

1 file changed

-9

lines changed

`‎src/pl/plpgsql/src/pl_exec.c`

Lines changed: 1 addition & 9 deletions

Original file line number	Diff line number	Diff line change
`@@ -1418,17 +1418,9 @@ exec_stmt_getdiag(PLpgSQL_execstate estate, PLpgSQL_stmt_getdiag stmt)`
`1418`	`1418`	`foreach(lc,stmt->diag_items)`
`1419`	`1419`	`{`
`1420`	`1420`	`PLpgSQL_diag_itemdiag_item= (PLpgSQL_diag_item)lfirst(lc);`
`1421`		`-PLpgSQL_datum*var;`
	`1421`	`+PLpgSQL_datum*var=estate->datums[diag_item->target];`
`1422`	`1422`	`boolisnull= false;`
`1423`	`1423`
`1424`		`-if (diag_item->target <=0)`
`1425`		`-continue;`
`1426`		`-`
`1427`		`-var=estate->datums[diag_item->target];`
`1428`		`-`
`1429`		`-if (var==NULL)`
`1430`		`-continue;`
`1431`		`-`
`1432`	`1424`	`switch (diag_item->kind)`
`1433`	`1425`	`{`
`1434`	`1426`	`casePLPGSQL_GETDIAG_ROW_COUNT:`

0 commit comments

Comments

(0)

Movatterモバイル変換

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Commit7bdf9b8

File tree

1 file changed

1 file changed

`‎src/pl/plpgsql/src/pl_exec.c`

0 commit comments