| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: TODO: trigger features |
| Date: | 2003-08-05 22:07:04 |
| Message-ID: | 200308052207.h75M74e23504@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andreas Pflug wrote:
> YATS (yet another TODO suggestion):
> provide an official and reliable way to temporarily enable/disable triggers.
> "ALTER TABLE xxx ENABLE/DISABLE TRIGGER ALL/trgName"
>
> We still have that nasty "not presently checked everywhere it should be"
> comment in the doc for pg_trigger...
> Yes, this could be achieved by dropping and recreating the trigger after
> importing, which I expect to be suggested by you ;-)
We already have that TODO:
* Allow triggers to be disabled [trigger]
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-08-05 22:12:17 | Re: Adjustment of spinlock sleep delays |
| Previous Message | scott.marlowe | 2003-08-05 22:06:01 | Re: logging stuff |