| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | Peter Erickson <redlamb(at)redlamb(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Cannot allocate memory for output buffer |
| Date: | 2009-11-28 16:42:03 |
| Message-ID: | 20091128164203.GA10880@svana.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Nov 27, 2009 at 05:55:30PM -0500, Peter Erickson wrote:
> Thanks. Out of curiosity, if memory exhaustion was the problem, any idea
> why the task manager would show that I'm only using 1.2GB of the 3GB of
> memory?
Note that what usually kills you first on 32-bit systems is that you
want 250MB of *contiguous* memory. Depending on how the program is
started and if you have memory map randomization, it becomes entirely
possible to have more than 1GB free, yet no blocks big enough to hold
250MB together.
64-bit systems don't suffer from this problem, the address space is so
large it's just not an issue.
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Please line up in a tree and maintain the heap invariant while
> boarding. Thank you for flying nlogn airlines.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-11-28 16:45:46 | Re: Strange "bug" in dump ? |
| Previous Message | Filip Rembiałkowski | 2009-11-28 15:45:41 | postgres log file mode |