| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>, Joe Conway <mail(at)joeconway(dot)com>, Laurette Cisneros <laurette(at)nextbus(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Disabling triggers (was Re: pgsql 7.2.3 crash) |
| Date: | 2002-10-14 04:13:39 |
| Message-ID: | 200210140413.g9E4Dds08169@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> I was wondering whether an ALTER TABLE command is really the right way
> to approach this. If we had an ALTER-type command, presumably the
> implication is that its effects would be global to all backends. But
> the uses that I've seen for suspending trigger invocations would be
> happier with a local, temporary setting that only affects the current
> backend. Any thoughts about that?
I think SET would be the proper place, but I don't see how to make it
table-specific.
--
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 | Joe Conway | 2002-10-14 04:15:08 | Re: Disabling triggers (was Re: pgsql 7.2.3 crash) |
| Previous Message | Bruce Momjian | 2002-10-14 04:12:10 | Re: \copy needs work (was Re: Changing Column Order) |