| From: | Marko Tiikkaja <marko(at)joh(dot)to> |
|---|---|
| To: | Mark Scheffer <pg2401k(at)pinkwin(dot)com> |
| Cc: | Pg Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #15060: Row in table not found when using pg function in an expression |
| Date: | 2018-02-12 13:56:28 |
| Message-ID: | CAL9smLAxp-Qi5noy9BWBEqQWkTO05Rfzio2sF0wcjsjJrJALSA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Feb 12, 2018 at 2:37 PM, Mark Scheffer <pg2401k(at)pinkwin(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guo Xiang Tan | 2018-02-12 14:13:45 | Re: BUG #15032: Segmentation fault when running a particular query |
| Previous Message | Mark Scheffer | 2018-02-12 13:37:47 | Re: BUG #15060: Row in table not found when using pg function in an expression |