From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
---|---|
To: | "Francisco Reyes" <lists(at)stringsutils(dot)com> |
Cc: | "PostgreSQL general" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_restore out of memory |
Date: | 2007-06-14 23:20:35 |
Message-ID: | 87y7imrum4.fsf@oxford.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Francisco Reyes" <lists(at)stringsutils(dot)com> writes:
> kern.maxdsiz="1600MB" #1.6GB
> kern.dfldsiz="1600MB" #1.6GB
> kern.maxssiz="128M" # 128MB
It ought to be maxdsiz which seems large enough.
> The error that I got was:
> pg_restore: [archiver (db)] Error from TOC entry 2146; 0 988154 TABLE DATA
> message_attachments pgsql
> pg_restore: [archiver (db)] COPY failed: ERROR: out of memory
> DETAIL: Failed on request of size 134217728 (128MB)
What does the output of "ulimit -a" show? Can you arrange to run ulimit -a in
the same environment as the server? Either by starting the server in shell
manually or by putting ulimit -a in the startup script which starts the server
if you have one?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Allison | 2007-06-14 23:54:30 | Re: DeadLocks..., DeadLocks... |
Previous Message | Gregory Stark | 2007-06-14 23:12:59 | Re: Hash Aggregate plan picked for very large table == out of memory |