From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | hyanchurevich(at)spotware(dot)com |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #17827: Rule on insert into table doesn't work when excepting select from the table itself |
Date: | 2023-03-09 15:01:48 |
Message-ID: | 377748.1678374108@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> create table tbl (id int);
> create table rule_stat (msg text, id int);
> create rule rule_tbl as on insert to tbl do insert into rule_stat
> values('Rule triggered for ',new.id);
> insert into tbl
> select 1
> except
> select id from tbl;
> table rule_stat; -- no rows
This is not a bug. The DO ALSO command executes after the original
INSERT command, and what it executes looks basically like
insert into rule_stat
select 'Rule triggered for ', id from
(select 1
except
select id from tbl);
But at this point we've already completed the original INSERT,
so now there is a row with id 1 in "tbl", and thus the EXCEPT
produces nothing.
While there are use-cases for this sort of behavior, most people
find that propagating data to another table is better done with
an AFTER trigger. It's far easier to understand what will happen.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Salavessa, Joao (Senior Developer) | 2023-03-09 15:33:50 | RE: [EXTERNAL] Re: PostgreSQL 14.7 "ALTER TABLE IF EXISTS" fails - ERROR: schema/relation "<name>" does not exist |
Previous Message | Tom Lane | 2023-03-09 14:51:19 | Re: PostgreSQL 14.7 "ALTER TABLE IF EXISTS" fails - ERROR: schema/relation "<name>" does not exist |