On Mar 16, 2011, at 2:31 AM, Andy Chambers wrote:
> Is it a big no-no to enable/disable triggers by manually setting
> pg_trigger.tgenabled to 'D'?
Not recommended to do anything with catalog tables. At the place of this use
following command:
ALTER TABLE DISABLE TRIGGER [ trigger_name | AL
On Tue, Mar 15, 2011 at 05:01:50PM -0400, Andy Chambers wrote:
> Is it a big no-no to enable/disable triggers by manually setting
> pg_trigger.tgenabled to 'D'?
No, but I seem to recall having seen corner cases where it didn't
work. (This was the reason that in older versions of slony, slony
fo
Hi All,
Is it a big no-no to enable/disable triggers by manually setting
pg_trigger.tgenabled to 'D'?
--
Andy Chambers
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
=?iso-8859-1?q?Germ=E1n_H=FCttemann_Arza?= <[EMAIL PROTECTED]> writes:
> Hello,
> I tried to execute ALTER TABLE emp DISABLE TRIGGER after_ins_emp on
> PostgreSQL
> 7.4.13 and I realised that feature isn't include yet in this version.
> How can I enable/disable a trigger in this version of Postg
Hello,
I tried to execute ALTER TABLE emp DISABLE TRIGGER after_ins_emp on PostgreSQL
7.4.13 and I realised that feature isn't include yet in this version.
How can I enable/disable a trigger in this version of PostgreSQL? Should I set
the attribute tgenabled from pg_trigger directly?
Hope you
