From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Prasad dev" <esteem3300(at)hotmail(dot)com> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: Disabling Trigger |
Date: | 2005-08-30 21:40:45 |
Message-ID: | 25010.1125438045@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
"Prasad dev" <esteem3300(at)hotmail(dot)com> writes:
> Currently i am using 8.0.3 , what i mean by it doesn't work is, when i set
> the tgenabled to FALSE for that particular trigger it still fires the
> trigger unless there is something more to it which i doesn't know.
If you start a fresh session, you'll probably find that it doesn't fire
the trigger anymore.
The trick is to get existing sessions to notice that you changed the
pg_trigger row; they don't watch for that. What they do watch for is
updates of pg_class, which is why a dummy update of the table's pg_class
row might help.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | operationsengineer1 | 2005-08-30 22:27:15 | Re: Copy Failure |
Previous Message | Tom Lane | 2005-08-30 21:36:52 | Re: pgsql installation problem! |