Skip site navigation (1) Skip section navigation (2)

0ut of Memory Error during Vacuum Analyze

From: "Tomeh, Husam" <htomeh(at)firstam(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: 0ut of Memory Error during Vacuum Analyze
Date: 2006-02-14 16:45:08
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
This is the second time I'm getting out of memory error when I start a
database vacuum or try to vacuum any table. Note this machine has been
used for data load batch purposes. 

=# vacuum analyze code;
ERROR:  out of memory
DETAIL:  Failed on request of size 1073741820.

I'm running Postgres 8.1.1 on RedHat 2.6 kernel (HP server). 
My maintenance work area never been changed. It's set to 1GB.
(maintenance_work_mem = 1048576). Physical memory: 32 GB.  

Bouncing the database does not help. 

Two workarounds I have used so far:

  1) Decreasing the maintenance_work_mem to 512MB, vacuum analyze would
work just fine.


  2) Bouncing the server (maintaining the original 1GB
maintenance_work_mem) would also work.

I have not had that error on the production instances (which are
identical copies of the loading instance) - only the loading instance..

Any explanation as to why and how to avoid that ?  Thanks

This message contains confidential information intended only for the use of the addressee(s) named above and may contain information that is legally privileged.  If you are not the addressee, or the person responsible for delivering it to the addressee, you are hereby notified that reading, disseminating, distributing or copying this message is strictly prohibited.  If you have received this message by mistake, please immediately notify us by replying to the message and delete the original message immediately thereafter.

Thank you.

                                   FADLD Tag


pgsql-performance by date

Next:From: Scott MarloweDate: 2006-02-14 16:50:35
Subject: Re: out of memory
Previous:From: martial.bizelDate: 2006-02-14 16:32:33
Subject: Re: out of memory

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group