Re: CREATE TABLE .. PARTITION OF fails to preserve tgenabled for inherited row triggers
| От | Justin Pryzby |
|---|---|
| Тема | Re: CREATE TABLE .. PARTITION OF fails to preserve tgenabled for inherited row triggers |
| Дата | |
| Msg-id | 20201015175724.GX9241@telsasoft.com обсуждение исходный текст |
| Ответ на | CREATE TABLE .. PARTITION OF fails to preserve tgenabled for inherited row triggers (Justin Pryzby <pryzby@telsasoft.com>) |
| Список | pgsql-hackers |
I'm hoping that Alvaro will comment on this.
On Wed, Sep 30, 2020 at 05:34:50PM -0500, Justin Pryzby wrote:
> CREATE TABLE t(i int) PARTITION BY RANGE(i);
> CREATE TABLE t1 PARTITION OF t FOR VALUES FROM (1) TO (10);
> CREATE OR REPLACE FUNCTION tgf() RETURNS trigger LANGUAGE plpgsql AS $$ begin raise exception 'except'; end $$;
> CREATE TRIGGER tg AFTER INSERT ON t FOR EACH ROW EXECUTE FUNCTION tgf();
> ALTER TABLE t1 DISABLE TRIGGER tg;
> INSERT INTO t VALUES(1); -- inserts when trigger is disabled: good
> ALTER TABLE t DISABLE TRIGGER tg;
> CREATE TABLE t2 PARTITION OF t FOR VALUES FROM (10) TO (20);
>
> postgres=# SELECT tgrelid::regclass, tgenabled FROM pg_trigger WHERE tgrelid::regclass::text IN ('t1','t2');
> tgrelid | tgenabled
> ---------+-----------
> t1 | D
> t2 | O
> (2 rows)
>
> I consider this a bug,but CreateTrigStmt doesn't have any "enabled" member
> (since it's impossible to CREATE TRIGGER .. DISABLED), so I'm not sure where
> the fix should be.
В списке pgsql-hackers по дате отправления: