"Francisco Reyes" <[EMAIL PROTECTED]> writes:
> On 1:00 pm 07/18/08 Tom Lane <[EMAIL PROTECTED]> 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
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
