| From: | John R Pierce <pierce(at)hogranch(dot)com> |
|---|---|
| To: | Angelo Nicolosi <amenuor(at)hotmail(dot)com> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: OOM on large SELECT |
| Date: | 2009-09-17 19:05:11 |
| Message-ID: | 4AB28867.5050105@hogranch.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Angelo Nicolosi wrote:
> Sorry for the delay of this answer but i was trying to figure out.
> However I saw that the memory that the postgres is using is getting
> larger step by step.
> So it doesn't free it.
> After the third query it is already full and one of the thread of the
> postgres is killed from the OOM.
> When the process is killed the program usually is going to call again
> a stored function.
> By the way the info that you required me are:
I wonder if the work_mem settings in postgresql.conf are too large for
this computer? if you're not the postgres administrator, you'll need
to work with them to identify this problem.
note, btw, 8.4.0 has been superceded by 8.4.1, with a lot of bug
fixes. painless inplace upgrade.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andre Rothe | 2009-09-18 08:24:32 | Wrong column default values |
| Previous Message | Joseph Shraibman | 2009-09-17 18:27:20 | Re: BUG #5058: [jdbc] Silent failure with executeUpdate() |