| From: | Flo <fluancefg(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Can't restore view with pg_restore |
| Date: | 2017-05-30 15:02:53 |
| Message-ID: | CAPW7RPkqjVSeHoCph5cSBQgfn92JYFNvnT+B9uS52jg20P74VA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hm, I don't know much about pglogical. Does it automatically add a
> trigger to every new table without user intervention? If so, that's
> kinda broken.
Honestly, I'm very surprised about that behaviour. I made few tests, and
yes, it seems that as soon as a new table is created using CREATE TABLE or
CREATE TABLE AS, there's a trigger automatically added.
I'm going to open a bug report on their side.
Regards,
Florian
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Muise | 2017-05-30 17:09:51 | Re: BUG #14662: 'has_table_privilege()' function fails with error, "invalid name syntax" when using Japanese symbols |
| Previous Message | Achilleas Mantzios | 2017-05-30 14:11:46 | Re: BUG #14679: Inconsistent/wrong behavior of pg_trigger_depth when used with DEFERRED CONSTRAINTS |