From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Johann Spies <jspies(at)sun(dot)ac(dot)za> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Out of memory |
Date: | 2011-07-21 14:36:56 |
Message-ID: | 25415.1311259016@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Johann Spies <jspies(at)sun(dot)ac(dot)za> 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
From | Date | Subject | |
---|---|---|---|
Next Message | David Ondrejik | 2011-07-21 14:44:37 | Re: vacuumdb question/problem |
Previous Message | Johann Spies | 2011-07-21 14:11:01 | Out of memory |