Re: BUG #15060: Row in table not found when using pg function in an expression - Mailing list pgsql-bugs

From Marko Tiikkaja
Subject Re: BUG #15060: Row in table not found when using pg function in an expression
Date
Msg-id CAL9smLAxp-Qi5noy9BWBEqQWkTO05Rfzio2sF0wcjsjJrJALSA@mail.gmail.com
Whole thread Raw
In response to Re: BUG #15060: Row in table not found when using pg function in anexpression  (Mark Scheffer <pg2401k@pinkwin.com>)
Responses Re: BUG #15060: Row in table not found when using pg function in anexpression  (Mark Scheffer <pg2401k@pinkwin.com>)
List pgsql-bugs
On Mon, Feb 12, 2018 at 2:37 PM, Mark Scheffer <pg2401k@pinkwin.com> wrote:
Significant is that function get_bug_id() being STABLE is necessary for the
bug to occur.
It appears to be not a bug, since documentation reads:

> For functions written in SQL or in any of the standard procedural
> languages, there is a second important property determined by the
> volatility category,
*
> namely the visibility of any data changes that have been made by the SQL
> command that is calling the function. A VOLATILE function will see such
> changes, a STABLE or IMMUTABLE function will not

I don't think this is relevant, since the changes were NOT made by the SQL command calling the function.  They were made by the INSERT which executed earlier in a VOLATILE function.


.m

pgsql-bugs by date:

Previous
From: Mark Scheffer
Date:
Subject: Re: BUG #15060: Row in table not found when using pg function in anexpression
Next
From: Guo Xiang Tan
Date:
Subject: Re: BUG #15032: Segmentation fault when running a particular query