Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 4BAE3B5DC1A for ; Thu, 21 Jul 2011 11:37:05 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 08839-07 for ; Thu, 21 Jul 2011 14:36:58 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id D2094B5DC02 for ; Thu, 21 Jul 2011 11:36:57 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id p6LEaumj025416; Thu, 21 Jul 2011 10:36:56 -0400 (EDT) To: Johann Spies cc: pgsql-admin@postgresql.org Subject: Re: Out of memory In-reply-to: <20110721141101.GA23173@sun.ac.za> References: <20110721141101.GA23173@sun.ac.za> Comments: In-reply-to Johann Spies message dated "Thu, 21 Jul 2011 16:11:01 +0200" Date: Thu, 21 Jul 2011 10:36:56 -0400 Message-ID: <25415.1311259016@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-3.093 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RP_MATCHES_RCVD=-1.193 X-Spam-Level: X-Archive-Number: 201107/152 X-Sequence-Number: 37931 Johann Spies writes: > On a computer with 2G Ram running Debian Squeeze and Postgresql 8.4.8-0squeeze2 > I made a dump using 'pg_dump kb > kb.sql'. > I copied the file to another computer with 8G RAM running Debian > wheezy/sid/Postgresql 8.4.8-2 and tried to load that data by running > 'psql -f kb.sql' - a process which produced a lot of errors ending with > psql:kb.sql:4189263: invalid command \N > psql:kb.sql:4189277: invalid command \N Almost always, when you get a cascade of error messages, the thing to look at is the *first* error, or first few errors. Not the last ones. In this case I'd guess that a COPY command failed and psql is now trying to process the COPY data as SQL commands, but you'll never be able to tell any more than that without seeing the error message that the COPY reported. regards, tom lane