Re: Disabling triggers with psql (gforge 7.4 to 8.2 migration)

On Wed, Feb 10, 2010 at 10:30 AM, Iñigo Martinez Lasala <imartinez@vectorsf.com> wrote:

Hmmmm...

What about
UPDATE pg_trigger SET tgenabled = false;

Restore data, and after done:
UPDATE pg_trigger SET tgenabled = true;

I'm going to test it.

Perhaps this was still a boolean column in 8.2, but at least in 8.3 and above tgenabled is a "char" field. The only explanation I found of its values is here:
http://archives.postgresql.org/pgsql-hackers/2007-01/msg01302.php

Anyway, I suspect your idea will work, but if you're going to the trouble of disabling+reenabling triggers for performance reasons, you might still be better off with pg_restore, since it can handle creation of constraints and indexes at the appropriate time as well, which can really help. 

Josh