From 2000info@netsite.com.br Fri Feb  20 03:28:54 2004
X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.2])
	by svr1.postgresql.org (Postfix) with ESMTP id D95CBD1C511
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Fri, 20 Feb 2004 03:28:54 +0000 (GMT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024)
	with ESMTP id 15910-09
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Thu, 19 Feb 2004 23:28:57 -0400 (AST)
Received: from smtp1.netsite.com.br (smtpweb.netsite.com.br [200.187.175.55])
	by svr1.postgresql.org (Postfix) with ESMTP id 2DCD2D1CAF3
	for <pgsql-sql@postgresql.org>; Thu, 19 Feb 2004 23:28:52 -0400 (AST)
Received: from nt2000 (ip-f159-202.idial.com.br [200.146.222.202])
	by smtp1.netsite.com.br (Postfix) with SMTP id 1D80C6D856
	for <pgsql-sql@postgresql.org>; Fri, 20 Feb 2004 00:28:25 -0300 (BRT)
Message-ID: <001e01c3f761$187b2d80$cade92c8@info2000.com.br>
From: "2000info" <2000info@netsite.com.br>
To: "PGSQL" <pgsql-sql@postgresql.org>
Subject: =?iso-8859-1?Q?pg=5Frestore_-_don=B4t_restore._Why=3F?=
Date: Fri, 20 Feb 2004 00:24:46 -0300
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_001B_01C3F747.F1AE8170"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4927.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200
X-Virus-Scanned: by amavisd-new at postgresql.org
X-Spam-Status: No, hits=0.2 tagged_above=0.0 required=5.0 tests=HTML_50_60,
	HTML_MESSAGE
X-Spam-Level: 
X-Archive-Number: 200402/298
X-Sequence-Number: 16988

This is a multi-part message in MIME format.

------=_NextPart_000_001B_01C3F747.F1AE8170
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

pg_dump, ok.
pg_restore, don=B4t restore. Why?

Red Hat 9, Fedora, Conectiva 9 and Postgres 7.4.1 make my ambient use.

pg_restore -i -v -N -etc... return:
Droping... error! Object does not exist...
                      OR
Creating... error! Object exist with the same arguments...
                      AND "Break the restore process".

Is this errors just in time for break the restore vital process?

------=_NextPart_000_001B_01C3F747.F1AE8170
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.3700.6699" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>pg_dump, ok.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>pg_restore, don=B4t restore. Why?</FONT></=
DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Red Hat 9, Fedora, Conectiva 9 and Postgre=
s 7.4.1=20
make my ambient use.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>pg_restore -i -v -N -etc... return:</FONT>=
</DIV>
<DIV><FONT face=3DArial size=3D2>Droping... error! Object does not=20
exist...</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
OR</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Creating... error! Object exist with the s=
ame=20
arguments...</FONT></DIV>
<DIV><FONT face=3DArial=20
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;AND=20
"Break the restore process".</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Is this errors just in time for break the =
restore=20
vital process?</FONT></DIV></BODY></HTML>

------=_NextPart_000_001B_01C3F747.F1AE8170--




From ajs@crankycanuck.ca Fri Feb  20 12:14:58 2004
X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.2])
	by svr1.postgresql.org (Postfix) with ESMTP id DC728D1E150
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Fri, 20 Feb 2004 12:14:58 +0000 (GMT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024)
	with ESMTP id 44994-06
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Fri, 20 Feb 2004 08:14:44 -0400 (AST)
Received: from fep02-mail.bloor.is.net.cable.rogers.com
	(fep02-mail.bloor.is.net.cable.rogers.com [66.185.86.72])
	by svr1.postgresql.org (Postfix) with ESMTP id C7985D1D570
	for <pgsql-sql@postgresql.org>; Fri, 20 Feb 2004 08:14:40 -0400 (AST)
Received: from phlogiston.dydns.org ([65.49.121.67])
	by fep02-mail.bloor.is.net.cable.rogers.com
	(InterMail vM.5.01.05.12 201-253-122-126-112-20020820) with ESMTP id
	<20040220121423.HMES181170.fep02-mail.bloor.is.net.cable.rogers.com@phlogiston.dydns.org>
	for <pgsql-sql@postgresql.org>; Fri, 20 Feb 2004 07:14:23 -0500
Received: by phlogiston.dydns.org (Postfix, from userid 1000)
	id AF2603F40; Fri, 20 Feb 2004 07:14:42 -0500 (EST)
Date: Fri, 20 Feb 2004 07:14:42 -0500
From: Andrew Sullivan <ajs@crankycanuck.ca>
To: PGSQL <pgsql-sql@postgresql.org>
Subject: Re: pg_restore - don?t restore. Why?
Message-ID: <20040220121442.GA15383@phlogiston.dyndns.org>
Mail-Followup-To: PGSQL <pgsql-sql@postgresql.org>
References: <001e01c3f761$187b2d80$cade92c8@info2000.com.br>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <001e01c3f761$187b2d80$cade92c8@info2000.com.br>
User-Agent: Mutt/1.5.4i
X-Authentication-Info: Submitted using SMTP AUTH LOGIN at
	fep02-mail.bloor.is.net.cable.rogers.com from [65.49.121.67]
	using ID <a.sullivan@rogers.com> at Fri,
	20 Feb 2004 07:14:23 -0500
X-Virus-Scanned: by amavisd-new at postgresql.org
X-Archive-Number: 200402/301
X-Sequence-Number: 16991

On Fri, Feb 20, 2004 at 12:24:46AM -0300, 2000info wrote:
> pg_dump, ok.
> pg_restore, don?t restore. Why?

If you didn't use a non-ASCII format from pg_dump, you don't need
pg_restore.  Just use psql.

A

-- 
Andrew Sullivan