Content-Type: text/plain;
  charset="iso-8859-1"
From: Josh Berkus <josh@agliodbs.com>
Reply-To: josh@agliodbs.com
Organization: Aglio Database Solutions
To: <mallah@trade-india.com>
Subject: Re: disabling triggers
Date: Tue, 17 Jun 2003 11:31:24 -0700
User-Agent: KMail/1.4.3
Cc: <pgsql-sql@postgresql.org>
References: <1164.219.65.230.103.1055871254.squirrel@mail.trade-india.com>
	<200306171058.44814.josh@agliodbs.com>
	<1175.219.65.230.103.1055873842.squirrel@mail.trade-india.com>
In-Reply-To: <1175.219.65.230.103.1055873842.squirrel@mail.trade-india.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200306171131.24578.josh@agliodbs.com>

Mallah,

> >> Is setting reltriggers=3D0 on pg_class an  accepatble way of
> >> disabling triggers on a table temporarily?
>=20
> Ok , but someone on list was scary few months back.

I've done it many times without a problem.  The trick is re-setting the=20
triggers to the correct number when you're done.  See the scripts that=20
pg_dump -a creates for a good example.

> Agreed , but there is no easy way to view current trigger defination of
> existing triggers before dropping from psql .

So?  Create a perl script.   It can:
1) query the system tables to find out the trigger definintion
	(you'll need pg_trigger, pg_proc, and pg_type)
2) generate a script to restore all the triggers to be used later;
3) drop all the triggers

Of course, setting reltriggers=3D0 is probably a lot easier.

--=20
-Josh Berkus
 Aglio Database Solutions
 San Francisco