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

Hmm...
No, I've not tried it. Does pg_dump perform some kind of truncating over
bad chars? If yes, my problem would be solved!

When actual test finish, I will try again with pg_dump from 8.2

Thank you, Alvaro.

-----Original Message-----
From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Iñigo Martinez Lasala <imartinez(at)vectorsf(dot)com>
Cc: pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: [ADMIN] Disabling triggers with psql (gforge 7.4 to 8.2
migration)
Date: Wed, 10 Feb 2010 13:21:04 -0300

Iñigo Martinez Lasala wrote:

> Third one, and we haven't been able to fix it, is we cannot restore data
> dump via psql due to psql does not have an option to disable triggers.
> So, when restoring data, it fails. So... is there any way to disable in
> a psql session all triggers same way like with pg_restore
> --disable-triggers? Or can we convert plain text dump to be processed
> by pg_restore? Perhaps a table by table trigger disabling script?

Have you tried using 8.2's pg_dump instead of the old one?

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support