| From: | Terry Lee Tucker <terry(at)esc1(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Disabling triggers in a transaction |
| Date: | 2005-03-03 16:07:46 |
| Message-ID: | 200503031107.46593.terry@esc1.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
This caught my eye the other day, but didn't take the time to examine it. I
find that I am now very interested in it. Could you please elaborate on your
method and how this works?
TIA
On Sunday 27 February 2005 05:37 pm, Jay Guerette saith:
> If I disable INSERT and UPDATE triggers inside a transaction; by
> setting and resetting reltriggers in pg_class; am I correct in
> thinking that this will disable triggers globally for that table for
> the duration of that transaction? So an INSERT or UPDATE to this
> table, outside of the transaction and within that precise timeframe,
> would NOT fire the trigger? If so, would the 'serializable ' isolation
> level be required in order to ensure this doesn't happen?
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-03-03 17:14:53 | Re: PL/Perl trusted throws error on example function |
| Previous Message | Tom Lane | 2005-03-03 15:25:01 | Re: Does IMMUTABLE have any effect on functions? |