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
Date: Tue, 21 Sep 2021 11:01:11 -0400
Message-ID: <1980152.1632236471@sss.pgh.pa.us> (raw)
In-Reply-To: <17199-1ab2561f0d94af92@postgresql.org>
References: <17199-1ab2561f0d94af92@postgresql.org>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, notegihu@confused.at, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17199: Calling stored procedure with stable function as argument results in wrong result
In-Reply-To: <1980152.1632236471@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox