| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Relyea, Mike" <Mike(dot)Relyea(at)xerox(dot)com> |
| Cc: | "Todd A(dot) Cook" <tcook(at)blackducksoftware(dot)com>, pgsql-general(at)postgresql(dot)org, "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu> |
| Subject: | Re: Out of memory error in 8.1.0 Win32 |
| Date: | 2006-06-22 19:23:56 |
| Message-ID: | 2762.1151004236@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
"Relyea, Mike" <Mike(dot)Relyea(at)xerox(dot)com> writes:
> I've zipped the results of EXPLAIN INSERT INTO "tblSummary" SELECT *
> FROM "qrySummary"; for my case. It's a zip file that I've renamed to
> .txt in order to get around the attachment being blocked by certain mail
> servers.
Egad, what a mess :-(. By my count you have 89 hash joins, 24 sorts,
and 8 hash aggregations in there. In total these will feel authorized
to use 121 times work_mem. Since you've got work_mem set to 256 meg,
an out-of-memory condition doesn't seem that surprising. You need to
make work_mem drastically smaller for this query. Or else break it down
into multiple steps.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2006-06-22 19:34:08 | Re: Out of memory error in 8.1.0 Win32 |
| Previous Message | Chris Browne | 2006-06-22 19:23:23 | Re: OT: publicly available databases? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2006-06-22 19:34:08 | Re: Out of memory error in 8.1.0 Win32 |
| Previous Message | Tom Lane | 2006-06-22 19:15:58 | Re: Out of memory error in 8.1.0 Win32 |