| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | John R Pierce <pierce(at)hogranch(dot)com> |
| Cc: | Guillaume Lelarge <guillaume(at)lelarge(dot)info>, David Kerr <dmk(at)mr-paradox(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: vacuumdb ERROR: out of memory |
| Date: | 2010-02-09 21:12:03 |
| Message-ID: | dcc563d11002091312y1d5ebf47rf69a10fe6c212f84@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Feb 9, 2010 at 1:55 PM, John R Pierce <pierce(at)hogranch(dot)com> wrote:
> Guillaume Lelarge wrote:
>>>
>>> is this a 64bit postgres build?
>>>
>>> if not, you're probably running out of virtual address space in the 32
>>> bit user space, which is limited to like 2gb.
>>>
>>>
>>
>> IIRC, the virtual address space in 32bit platforms is 4GB.
>>
>
> it is, but within that 4gb, the kernel uses the top 1gb, so there's 3gb left
> for user program space in each process. shared memory, runtime libraries,
> etc all hve to come out of this 3gb user space
Note that any modern 32bit linux (oxymoron there, but anyway) can run
with PAE enabled and access far more than just 3GB of memory.
However, no single user space app can hit more than 2 or 3 (I forget
which) at a time.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Asher Hoskins | 2010-02-09 21:41:26 | Re: Best way to handle multi-billion row read-only table? |
| Previous Message | Steve Atkins | 2010-02-09 20:56:00 | Re: SSL connection lost after long-lasting copy command |