From: | Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz> |
---|---|
To: | pgsql-performance(at)lists(dot)postgresql(dot)org |
Subject: | Re: Out of Memory errors are frustrating as heck! |
Date: | 2019-04-16 22:39:26 |
Message-ID: | 3f964125-c216-b9e3-0d52-05959b9e69c2@archidevsys.co.nz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On 15/04/2019 08:23, Gunther wrote:
>
> For weeks now, I am banging my head at an "out of memory" situation.
> There is only one query I am running on an 8 GB system, whatever I
> try, I get knocked out on this out of memory. It is extremely
> impenetrable to understand and fix this error. I guess I could add a
> swap file, and then I would have to take the penalty of swapping. But
> how can I actually address an out of memory condition if the system
> doesn't tell me where it is happening?
>
[...]
I strongly suigest having a swap file, I've got 32GB, and I've used
2.9GB of my swap space after 4 days, but I'm not really pushing my
system. For me, mostly stuff that is only used once, or not at all, is
swapped out. If you do have a memory leak, then it might be easier to
diagnose, if you don't run out on Memory.
I suspect that most things will run a little better with some swap space.
Cherers,
Gavin
From | Date | Subject | |
---|---|---|---|
Next Message | Gunther | 2019-04-17 02:24:53 | Re: Out of Memory errors are frustrating as heck! |
Previous Message | Tom Lane | 2019-04-16 19:43:33 | Re: Out of Memory errors are frustrating as heck! |