Received: from maia.hub.org (unknown [200.46.208.211])
	by mail.postgresql.org (Postfix) with ESMTP id 57451632202
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Wed, 10 Feb 2010 12:59:59 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia,
	port 10024) with ESMTP id 95734-02-7
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Wed, 10 Feb 2010 16:59:47 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from hermes.vectorsf.com (firewall.vectorsf.com [62.82.80.62])
	by mail.postgresql.org (Postfix) with ESMTP id 4A1AC6348FF
	for <pgsql-admin@postgresql.org>; Wed, 10 Feb 2010 12:59:40 -0400 (AST)
Received: from localhost (localhost.localdomain [127.0.0.1])
	by hermes.vectorsf.com (Postfix) with ESMTP id 2414C11C003F;
	Wed, 10 Feb 2010 17:59:36 +0100 (CET)
X-Virus-Scanned: amavisd-new at hermes.vectorsf.com
Received: from hermes.vectorsf.com ([127.0.0.1])
	by localhost (hermes.vectorsf.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id mLBNNQbx+xlc; Wed, 10 Feb 2010 17:59:31 +0100 (CET)
Received: from [10.70.4.200] (deimos.vectorsf.com [10.70.4.200])
	(Authenticated sender: imartinez)
	by hermes.vectorsf.com (Postfix) with ESMTP id 9688611C003E;
	Wed, 10 Feb 2010 17:59:31 +0100 (CET)
Subject: Re: Disabling triggers with psql (gforge 7.4 to 8.2
 migration)
From: =?ISO-8859-1?Q?I=F1igo?= Martinez Lasala <imartinez@vectorsf.com>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
In-Reply-To: <20100210162104.GE4922@alvh.no-ip.org>
References: <99024f5f1002071922j5b14c350mb1612313690f16ec@mail.gmail.com>
	<87k4umg0c3.fsf@hi-media-techno.com> <1265794218.3714.12.camel@coyote>
	<20100210162104.GE4922@alvh.no-ip.org>
Content-Type: multipart/alternative; boundary="=-CxesRqfQAStYaGBvTo3Z"
Date: Wed, 10 Feb 2010 17:59:33 +0100
Message-ID: <1265821173.6369.32.camel@coyote>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.1 
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-2.598 tagged_above=-10 required=5 tests=AWL=-0.000,
	BAYES_00=-2.599, HTML_MESSAGE=0.001
X-Spam-Level: 
X-Archive-Number: 201002/83
X-Sequence-Number: 33686


--=-CxesRqfQAStYaGBvTo3Z
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit

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@commandprompt.com>
To: Iñigo Martinez Lasala <imartinez@vectorsf.com>
Cc: pgsql-admin <pgsql-admin@postgresql.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




--=-CxesRqfQAStYaGBvTo3Z
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.28.1">
</HEAD>
<BODY>
Hmm...<BR>
No, I've not tried it. Does pg_dump perform some kind of truncating over bad chars? If yes, my problem would be solved!<BR>
<BR>
When actual test finish, I will try again with pg_dump from 8.2<BR>
<BR>
Thank you, Alvaro.<BR>
<BR>
-----Original Message-----<BR>
<B>From</B>: Alvaro Herrera &lt;<A HREF="mailto:Alvaro%20Herrera%20%3calvherre@commandprompt.com%3e">alvherre@commandprompt.com</A>&gt;<BR>
<B>To</B>: I&#241;igo Martinez Lasala &lt;<A HREF="mailto:%3d%3fISO-8859-1%3fQ%3fI%3dF1igo%3f%3d%20Martinez%20Lasala%20%3cimartinez@vectorsf.com%3e">imartinez@vectorsf.com</A>&gt;<BR>
<B>Cc</B>: pgsql-admin &lt;<A HREF="mailto:pgsql-admin%20%3cpgsql-admin@postgresql.org%3e">pgsql-admin@postgresql.org</A>&gt;<BR>
<B>Subject</B>: Re: [ADMIN] Disabling triggers with psql (gforge 7.4 to 8.2 migration)<BR>
<B>Date</B>: Wed, 10 Feb 2010 13:21:04 -0300<BR>
<BR>
<PRE>
I&#241;igo Martinez Lasala wrote:

&gt; Third one, and we haven't been able to fix it, is we cannot restore data
&gt; dump via psql due to psql does not have an option to disable triggers.
&gt; So, when restoring data, it fails. So... is there any way to disable in
&gt; a psql session all triggers same way like with pg_restore
&gt; --disable-triggers?  Or can we convert plain text dump to be processed
&gt; 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                                <A HREF="http://www.CommandPrompt.com/">http://www.CommandPrompt.com/</A>
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

</PRE>
<BR>
</BODY>
</HTML>

--=-CxesRqfQAStYaGBvTo3Z--