From: | Mark Scheffer <pg2401k(at)pinkwin(dot)com> |
---|---|
To: | 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 14:20:09 |
Message-ID: | 1518445209487-0.post@n3.nabble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Marko Tiikkaja-4 wrote
> 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.
Yes I should have read a few lines further, and wake up:
> Because of this snapshotting behavior, a function containing only SELECT
> commands can safely be marked STABLE, even if it selects from tables that
> might be undergoing modifications by concurrent queries. PostgreSQL will
> execute all commands of a STABLE function using the snapshot established
> for the calling query, and so it will see a fixed view of the database
> throughout that query.
Sorry for inconvenience. Hope the VOLATILE-STABLE difference in behavior
helps in resolving this bug.
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-bugs-f2117394.html
From | Date | Subject | |
---|---|---|---|
Next Message | 石勇虎 | 2018-02-12 15:02:04 | response time is very long in PG9.5.5 using psql or jdbc |
Previous Message | Guo Xiang Tan | 2018-02-12 14:13:45 | Re: BUG #15032: Segmentation fault when running a particular query |