Ron writes:
> On 5/29/19 8:26 AM, Tom Lane wrote:
>> 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
>
>Are CTEs still optimization fences?
>https://www.2ndquadrant.com/en/blog/postgresql-ctes-are-optimization-fences/
Yes, but not in 12.
Regards, Andreas
--
2ndQuadrant - The PostgreSQL Support Company
On 5/29/19 8:26 AM, Tom Lane wrote:
PegoraroF10 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 p
PegoraroF10 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
Well, I think is not a transaction problem, because if you do the same thing
on a DO it will work.
DO $$
declare vMaster_ID integer;
begin
insert into Master(Customer_ID, Field2) values(1, 'BlaBla') returning
Master_ID into vMaster_ID;
insert into Detail(Master_ID, Product_ID, ProductValue)
Em qua, 29 de mai de 2019 às 08:52, PegoraroF10
escreveu:
>
> 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 ?
>
> with
> Master(Master_ID) as (insert into Master(Customer_ID, Fi
On Wed, 29 May 2019 at 12:52, PegoraroF10 wrote:
> This trigger will not work because Master record was not inserted yet.
>
That seems reasonable. Since the transaction is meant to be atomic any
select within the query should return data from tables as they are at the
start of the transaction, t
