| From: | Ragnar Kjørstad <postgres(at)ragnark(dot)vestdata(dot)no> |
|---|---|
| To: | Reiner Dassing <dassing(at)wettzell(dot)ifag(dot)de> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Restoring a pg_dump fails with |
| Date: | 2001-04-26 16:35:49 |
| Message-ID: | 20010426183549.E26041@vestdata.no |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Thu, Apr 26, 2001 at 05:35:02PM +0200, Reiner Dassing wrote:
> By upgrading von PostgreSQL 6.5.3 to 7.1.0 I restored a dump file by
> psql dbname <dbname.dump
>
> After some time I get the following message:
> ERROR: copy: line 1638280, Memory exhausted in AllocSetAlloc(56)
> PQendcopy: resetting connection
>
> The total number of lines is about 10 Millions!
>
> Can anybody help me or explain what to do?
> May be, I have to convert to INSERT-statements?
It's probably easier to cut the command into several smaller COPY
commands. All it takes is a small
awk/perl/python/your_favourite_scripting_language_here thing.
--
Ragnar Kjørstad
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Heller | 2001-04-26 16:55:46 | Re: 7.1 performance |
| Previous Message | Tom Lane | 2001-04-26 16:23:16 | Re: Restoring a pg_dump fails with |