Re: Vacuum analyse after a long time without one ... - Mailing list pgsql-admin

From Plugge, Joe R.
Subject Re: Vacuum analyse after a long time without one ...
Date
Msg-id BD69807DAE0CE44CA00A8338D0FDD08341278F7C@oma00cexmbx03.corp.westworlds.com
Whole thread Raw
In response to Re: Vacuum analyse after a long time without one ...  (Nicolas Michel <nicolas.michel@lemail.be>)
List pgsql-admin
I think Mr. Lane meant that you may have set the maintenance_work_mem setting too high, try setting it to about 25% of
thetotal RAM on your system for now. 

-----Original Message-----
From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Nicolas Michel
Sent: Friday, September 11, 2009 10:37 AM
To: Tom Lane
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Vacuum analyse after a long time without one ...

Tom Lane a écrit :
> Nicolas Michel <nicolas.michel@lemail.be> writes:
>> I have a problem with a database. The last full vacuum analyse was made
>> long time ago... So I tried to start launching a vacuum analyse and I
>> get this error :
>
>> $ vacuumdb -az
>> vacuumdb: vacuuming database "postgres"
>> VACUUM
>> vacuumdb: vacuuming database "mexi"
>> vacuumdb: vacuuming of database "mexi" failed: ERROR:  out of memory
>> DETAIL:  Failed on request of size 134697600.
>
> What is your maintenance_work_mem setting?  It rather looks like it's
> more than your system will really allow.
>
>             regards, tom lane
>
I already tried to set the work_mem setting to the max value I can but
it changed nothing.

--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin

pgsql-admin by date:

Previous
From: Lewis Kapell
Date:
Subject: Re: Vacuum analyse after a long time without one ...
Next
From: Nicolas Michel
Date:
Subject: Re: Vacuum analyse after a long time without one ...