| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Satoshi Nagayasu <nagayasus(at)nttdata(dot)co(dot)jp>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCHES] enable/disable trigger (Re: Fwd: Open items) |
| Date: | 2005-08-16 02:18:15 |
| Message-ID: | 20737.1124158695@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Oh, and one trick for disabling triggers in a single session is to do
> this:
> BEGIN WORK;
> ALTER TABLE xx DISABLE TRIGGER ALL
> ...
> ALTER TABLE xx ENABLE TRIGGER ALL
> COMMIT WORK;
> In this case, the triggers are disabled just for that session.
... but everybody else is locked out completely, because the ALTER takes
an exclusive lock on the table. It's a bit misleading to describe that
as a local change.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2005-08-16 02:19:56 | Re: Upcoming back-branch releases |
| Previous Message | Tom Lane | 2005-08-16 02:14:50 | Re: Upcoming back-branch releases |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-08-16 02:33:37 | Re: [PATCHES] enable/disable trigger (Re: Fwd: Open items) |
| Previous Message | Bruce Momjian | 2005-08-16 01:55:15 | Re: [PATCHES] enable/disable trigger (Re: Fwd: Open items) |