Re: BUG #17199: Calling stored procedure with stable function as argument results in wrong result
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: notegihu@confused.at
Cc: pgsql-bugs@lists.postgresql.org
Date: 2021-09-21T15:01:11Z
Lists: pgsql-bugs
PG Bug reporting form <noreply@postgresql.org> writes: > When a function that returns just a row count of a table is marked as STABLE > and is called from a stored procedure as argument, the result of the > function is different than when the function is called beforehand and stored > to a local variable. Ugh. Looks like I broke this in 84f5c2908, by not thinking about the possibility that a CALL's argument expressions would need an up-to-date snapshot. Will fix, thanks for the report! regards, tom lane
Commits
-
Fix misevaluation of STABLE parameters in CALL within plpgsql.
- 2ad5f963e130 14.0 landed
- 4476bcb8773b 15.0 landed
- e8b0bcae63ff 12.9 landed
- 5f0a073cbbf8 13.5 landed
- 13921c511266 11.14 landed