DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=subject:mime-version:content-type:from:in-reply-to:date:cc
	:message-id:references:to:x-mailer;
	b=iXciU2P/yWNY+nj+IlpsuNgCGGDgepspzr3o3vix0x1Ua3hEQV95aOp4TzNoX3ei0i
	GIjWN/Q/dEEMYaH1S+Wp4mQ4KU8LL+nAdnRfRroHDk3oCgCyRCLAG2aBUWfL4ywKAWWW
	879rKr+XBSwN+6HAOtqLTbRT78WBje/1KXyjI=
Subject: Re: Disabling triggers with psql (gforge 7.4 to 8.2 migration)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: multipart/alternative; boundary=Apple-Mail-14--256293142
From: Josh Kupershmidt <schmiddy@gmail.com>
In-Reply-To: <1265794218.3714.12.camel@coyote>
Date: Wed, 10 Feb 2010 09:55:15 -0500
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Message-Id: <971254BD-6919-41BB-8D26-160C14D5BFE2@gmail.com>
References: <99024f5f1002071922j5b14c350mb1612313690f16ec@mail.gmail.com>
	<87k4umg0c3.fsf@hi-media-techno.com>
	<1265794218.3714.12.camel@coyote>
To: =?iso-8859-1?Q?I=F1igo_Martinez_Lasala?= <imartinez@vectorsf.com>


--Apple-Mail-14--256293142
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Feb 10, 2010, at 4:30 AM, I=F1igo Martinez Lasala wrote:
>=20
> 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?

How about:
 1. restore your schema, with triggers, using a pg_dump --schema-only =
... ; pg_restore ...=20
 2. Create a psql-loadable data-only dump using pg_dump --data-only =
--disable-triggers --format=3Dp ...
 3. clean the data-only dump and restore

Or, you could do a full pg_dump -Fc ... of your database, then use =
pg_restore to restore the compressed dumpfile into a plaintext file =
(i.e. pg_restore [options] filename). Then run your cleanup on the =
plaintext file, and reload.=20

Josh=

--Apple-Mail-14--256293142
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Feb 10, 2010, at 4:30 AM, I=F1igo Martinez Lasala =
wrote:</div><blockquote type=3D"cite"><div><font =
class=3D"Apple-style-span" color=3D"#000000"><br></font>
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?&nbsp; Or can we convert plain text dump to be =
processed by pg_restore? Perhaps a table by table trigger disabling =
script?<br></div></blockquote></div><br><div>How =
about:</div><div>&nbsp;1. restore your schema, with triggers, using a =
pg_dump --schema-only ... ; pg_restore ...&nbsp;</div><div>&nbsp;2. =
Create a psql-loadable data-only dump using pg_dump --data-only =
--disable-triggers --format=3Dp ...</div><div>&nbsp;3. clean the =
data-only dump and restore</div><div><br></div><div>Or, you could do a =
full pg_dump -Fc ... of your database, then use pg_restore to restore =
the compressed dumpfile into a plaintext file (i.e. pg_restore [options] =
filename). Then run your cleanup on the plaintext file, and =
reload.&nbsp;</div><div><br></div><div>Josh</div></body></html>=

--Apple-Mail-14--256293142--