Re: Vacuum analyse after a long time without one ...

From: "Plugge, Joe R(dot)" <JRPlugge(at)west(dot)com>
To: Nicolas Michel <nicolas(dot)michel(at)lemail(dot)be>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Vacuum analyse after a long time without one ...
Date: 2009-09-11 15:40:03
Message-ID: BD69807DAE0CE44CA00A8338D0FDD08341278F7C@oma00cexmbx03.corp.westworlds.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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 the total RAM on your system for now.

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

Tom Lane a écrit :
> Nicolas Michel <nicolas(dot)michel(at)lemail(dot)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.

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Lewis Kapell 2009-09-11 15:41:43 Re: Vacuum analyse after a long time without one ...
Previous Message Tom Lane 2009-09-11 15:39:15 Re: Vacuum analyse after a long time without one ...