Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id B7F832E3358 for ; Tue, 8 Jan 2008 16:31:44 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 80976-09 for ; Tue, 8 Jan 2008 16:31:40 -0400 (AST) Received: from mail.scharp.org (MAIL.SCHARP.ORG [140.107.164.89]) by postgresql.org (Postfix) with ESMTP id 7E0522E329B for ; Tue, 8 Jan 2008 16:30:25 -0400 (AST) Received: from [10.6.164.25] (netapp [140.107.164.65]) by mail.scharp.org (8.13.6+Sun/8.13.6) with ESMTP id m08KUOsv000067 for ; Tue, 8 Jan 2008 12:30:24 -0800 (PST) Message-ID: <4783DDD7.2030900@scharp.org> Date: Tue, 08 Jan 2008 12:32:23 -0800 From: Mija Lee User-Agent: Thunderbird 2.0.0.6 (X11/20070802) MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: -d option in pg_dump Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/89 X-Sequence-Number: 27863 Hi - In previous versions of postgres (8.1, 8.0), we had problems loading some data from dumps that were used the copy command rather than the insert command. If I remember correctly, these problems were caused by weird characters in some of the data values. As a result, we tend to use the -d option with pg_dump. At this point our databases are taking too long to reload using inserts. I did some testing and haven't run into the problems with the copy commands but don't want to find out that I was wrong when I'm trying to restore from a failure. Were there changes made some time before 8.2.4 that made loading pg_dump with copy as safe as with insert commands? Have other people had problems restoring databases from pg_dump without the -d option? Mija