| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | lists(at)stringsutils(dot)com |
| Cc: | alvherre(at)commandprompt(dot)com, dev(at)archonet(dot)com, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Reducing memory usage of insert into select operations? |
| Date: | 2008-07-18 19:55:58 |
| Message-ID: | 8616.1216410958@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Francisco Reyes" <lists(at)stringsutils(dot)com> writes:
> On 1:00 pm 07/18/08 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> If you can get Postgres to report an actual out-of-memory error (as
>> opposed to crashing from OOM kill)
>> then it should dump a memory usage
>> map into the postmaster log. Looking at that would be informative.
> Got it.
> AfterTriggerEvents: 10553909248 total in 1268 blocks; 20432 free (6
> chunks); 10553888816 used
Well, that's definitely your problem ...
> HashBatchContext: 532676656 total in 74 blocks; 1863936 free (5
> chunks); 530812720 used
> HashBatchContext: 415227952 total in 59 blocks; 6589744 free (5
> chunks); 408638208 used
although these numbers seem way outta line too. What did you say you
had work_mem set to?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Francisco Reyes | 2008-07-18 20:16:42 | Re: Reducing memory usage of insert into select operations? |
| Previous Message | Francisco Reyes | 2008-07-18 17:25:38 | Re: Reducing memory usage of insert into select operations? |