From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | Matt Magoffin <postgresql(dot)org(at)msqr(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Out of memory on SELECT in 8.3.5 |
Date: | 2009-02-09 20:57:39 |
Message-ID: | 20090209205739.GI8123@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
* Scott Marlowe (scott(dot)marlowe(at)gmail(dot)com) wrote:
> I think that you're fixing a symptom, but ignoring the cause.
> Twiddling VM parameters may help out, but this problem of too much
> memory allocated is the real issue, so yeah, you're just putting off
> the inevitable.
I don't think changing work_mem down is actually going to reduce the
memory allocated without changing the plan to something less optimal.
In the end, all of this is putting off the inevitable, if you get enough
PGs going and enough requests and whatnot, you're going to start running
out of memory again. Same if you get larger data sets that take up more
hash table space or similar. Eventually you might need a bigger box,
but let's try to get everything in the current box to at least be used
first..
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Matt Magoffin | 2009-02-09 20:58:00 | Re: Out of memory on SELECT in 8.3.5 |
Previous Message | Stephen Frost | 2009-02-09 20:45:37 | Re: Out of memory on SELECT in 8.3.5 |