| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | Francisco Reyes <lists(at)stringsutils(dot)com> |
| Cc: | Douglas McNaught <doug(at)mcnaught(dot)org>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Reducing memory usage of insert into select operations? |
| Date: | 2008-07-18 16:03:49 |
| Message-ID: | 20080718160349.GA27000@svana.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Jul 18, 2008 at 10:40:02AM -0400, Francisco Reyes wrote:
> Found that yesterday (vm.overcommit_memory=2).
> Agree that this is better than OOM. I still ran out of memory last night
> and postgres just failed on the malloc(), which as you mentioned is better.
>
> Reduced work_mem to 8MB and trying again.
Perhaps you can try reducing the shared_buffers, to see if that helps
more? 8MB is quite small for workmem. More shared_buffers is not
necessarily better.
Also, how much swap are you running? overcommit disabled while not
having any swap setup is a great way to ensure you run out of memory
quickly.
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 | Suresh_ | 2008-07-18 16:07:37 | Writing a user defined function |
| Previous Message | Francisco Reyes | 2008-07-18 16:00:29 | Re: Reducing memory usage of insert into select operations? |