From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
Cc: | pgsql-hackers(at)postgresql(dot)org, hubert depesz lubaczewski <depesz(at)gmail(dot)com> |
Subject: | Re: problem with large maintenance_work_mem settings and |
Date: | 2006-03-04 16:25:24 |
Message-ID: | 14958.1141489524@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> writes:
>> not that I think it is related to the problem at all. It looks like I'm
>> hitting the MaxAllocSize Limit in src/include/utils/memutils.h.
> just tried to increase this limit to 4GB (from the default 1GB) and this
> seems to help a fair bit.
s/help a fair bit/break a whole lot of stuff/
There are reasons for that limit, and you can't just arbitrarily
rejigger it.
The sorting code probably needs a defense to keep it from trying to
exceed MaxAllocSize for the SortObject array; AFAIR there is no such
consideration there now, but it's easily added. I'm not sure where your
VACUUM failure is coming from though --- can you get a back trace from
the errfinish call in that case?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2006-03-04 16:37:12 | Re: Building Windows Server Extensions Using VC++ 2005 |
Previous Message | Bruce Momjian | 2006-03-04 16:23:13 | Re: Building Windows Server Extensions Using VC++ 2005 |