[HACKERS] PG10 transition tables, wCTEs and multiple operations on the same table - Mailing list pgsql-hackers

From Marko Tiikkaja
Subject [HACKERS] PG10 transition tables, wCTEs and multiple operations on the same table
Date
Msg-id CAL9smLCDQ=2o024rBgtD4WihzX8B3C6u_oSQ2K3+R5grJrV0bg@mail.gmail.com
Whole thread Raw
Responses Re: [HACKERS] PG10 transition tables, wCTEs and multiple operations on the same table
List pgsql-hackers
Since the subject of transition tables came up, I thought I'd test how this case works:

=# create table qwr(a int);
CREATE TABLE

=# create function qq() returns trigger as $$ begin raise notice '%', (select count(*) from oo); return null; end $$ language plpgsql;
CREATE FUNCTION

=# create trigger xx after insert on qwr referencing new table as oo for each statement execute procedure qq();
CREATE TRIGGER

=# with t as (insert into qwr values (1)) insert into qwr values (2), (3);
NOTICE:  3
NOTICE:  3
INSERT 0 2

to me, this means that it doesn't work.  Surely one of the trigger invocations should say 1, and the other 2.  Or was this intentional?


.m

pgsql-hackers by date:

Previous
From: Rafia Sabih
Date:
Subject: Re: [HACKERS] Default Partition for Range
Next
From: Craig Ringer
Date:
Subject: Re: [HACKERS] Do we need the gcc feature "__builtin_expect" topromote the branches prediction?