From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: with and trigger |
Date: | 2019-05-29 15:05:36 |
Message-ID: | 3ae9c51b-2552-a7e9-bbc5-f3d385461f74@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 5/29/19 8:26 AM, Tom Lane wrote:
> PegoraroF10 <marcos(at)f10(dot)com(dot)br> writes:
>> We like to use With to insert, update and return some value to user. But some
>> informations of those related tables are not available on that time, is that
>> a bug ?
> No, see the "WITH Clause" section of the SELECT reference page:
>
> The primary query and the WITH queries are all (notionally) executed
> at the same time. This implies that the effects of a data-modifying
> statement in WITH cannot be seen from other parts of the query, other
> than by reading its RETURNING output. If two such data-modifying
> statements attempt to modify the same row, the results are
> unspecified.
>
> This doesn't explicitly talk about triggers, but I think our attitude
> about the case you're discussing is that the results are unspecified.
> If a trigger fired in one WITH arm tries to look at the table(s)
> modified by other WITH arms, it might or might not see those changes.
Are CTEs still optimization fences?
https://www.2ndquadrant.com/en/blog/postgresql-ctes-are-optimization-fences/
--
Angular momentum makes the world go 'round.
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Kretschmer | 2019-05-29 15:12:03 | Re: with and trigger |
Previous Message | Adrian Klaver | 2019-05-29 14:28:24 | Re: psql: FATAL: the database system is starting up |