Re: Disabling triggers (was Re: pgsql 7.2.3 crash) - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Disabling triggers (was Re: pgsql 7.2.3 crash)
Date
Msg-id 200210140413.g9E4Dds08169@candle.pha.pa.us
Whole thread Raw
In response to Disabling triggers (was Re: pgsql 7.2.3 crash)  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: \copy needs work (was Re: Changing Column Order)
Next
From: Bruce Momjian
Date:
Subject: Re: experiences with autocommit functionality in 7.3