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-15 13:17:46 |
Message-ID: | 87hcp9cq6d.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:
> Gregory Stark writes:
>
>> You're right that your limit is above 128M but the error just means it tried
>> to allocated 128M and failed, it may already have allocated 400M and been
>> trying to go over the 524M mark.
>
> My limit should be 1.6GB as per /boot/loader.conf
Well according to "limit" it was 524M. I don't know how that relates to the
kernel limits you see in /boot/loader.conf. It may be the same thing but being
lowered by something in the startup scripts or it may be unrelated.
> The question is, what type of memory is that trying to allocate?
> Shared memory?
If it couldn't allocate the shared memory it wanted it wouldn't start up.
> The FreeBSD default is to cap programs at 512MB so thet fact the program is
> crashing at 1011MB means that the /boot/loader.conf setting of 1.6GB memory cap
> is active.
I'm skeptical that you can trust ps's VSZ reporting at this level of detail.
On some platforms VSZ includes a proportionate share of its shared memory or
might not include memory allocated but not actually written to yet (due to
copy-on-write).
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2007-06-15 13:19:37 | Re: pg_restore out of memory |
Previous Message | A. Kretschmer | 2007-06-15 13:00:31 | Re: Historical Data Question |