From: Tom Lane <tgl@sss.pgh.pa.us>
To: notegihu@confused.at
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17199: Calling stored procedure with stable function as
 argument results in wrong result
In-reply-to: <17199-1ab2561f0d94af92@postgresql.org>
References: <17199-1ab2561f0d94af92@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Tue, 21 Sep 2021 12:52:14 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1980151.1632236471.1@sss.pgh.pa.us>
Date: Tue, 21 Sep 2021 11:01:11 -0400
Message-ID: <1980152.1632236471@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1980152.1632236471%40sss.pgh.pa.us>
Precedence: bulk

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