From: | Soni M <diptatapa(at)gmail(dot)com> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | pg_dump with disable trigger |
Date: | 2018-04-10 23:17:41 |
Message-ID: | CAAMgDXneQvt1yX6u7XL=LBrAPU1D=tRKCgz6_JGL7+VBHNB5mQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hello All,
I think I found bug on pg_dump 9.6.8.
The bug arise when using pg_dump with --disable-trigger option.
The command just :
pg_dump -f /tmp/test_disable_trigger.sql -a -b --disable-triggers -t
some_table some_database
On the resulted script, it simply did
ALTER TABLE public.some_table DISABLE TRIGGER ALL;
COPY command
ALTER TABLE public.some_table ENABLE TRIGGER ALL;
This become a problem, when the destination table already has Disabled user
triggers, it gets enabled by the dump script.
It also altered another kind of trigger like Triggers firing on replica
only, get altered to ordinary triggers.
Thanks
--
Regards,
Soni Maula Harriz
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2018-04-10 23:46:46 | Re: pg_dump with disable trigger |
Previous Message | Tom Lane | 2018-04-10 22:40:43 | Re: BUG #15105: OpenTransientFile() should be paired with CloseTransientFile() rather than close() |