Re: VACUUM FULL out of memory - Mailing list pgsql-hackers

From Tom Lane
Subject Re: VACUUM FULL out of memory
Date
Msg-id 24230.1199735010@sss.pgh.pa.us
Whole thread Raw
In response to Re: VACUUM FULL out of memory  (Michael Akinde <michael.akinde@met.no>)
Responses Re: VACUUM FULL out of memory  (Michael Akinde <michael.akinde@met.no>)
List pgsql-hackers
Michael Akinde <michael.akinde@met.no> writes:
> As suggested, I tested a VACUUM FULL ANALYZE with 128MB shared_buffers 
> and 512 MB reserved for maintenance_work_mem (on a 32 bit machine with 4 
> GB RAM). That ought to leave more than enough space for other processes 
> in the system. Again, the system fails on the VACUUM with the following 
> error (identical to the error we had when maintenance_work_mem was very 
> low.

> INFO:  vacuuming "pg_catalog.pg_largeobject"
> ERROR:  out of memory
> DETAIL:  Failed on request of size 536870912

Are you sure this is a VACUUM FULL, and not a plain VACUUM?  I suspect
that it's the latter, and the reason it's failing is that you are
running the postmaster under a ulimit that is less than 512MB (or at
least not enough more to allow an allocation of that size).
        regards, tom lane


pgsql-hackers by date:

Previous
From: ilanco@gmail.com
Date:
Subject: ERROR: translation failed from server encoding to wchar_t
Next
From: ilanco@gmail.com
Date:
Subject: Re: ERROR: translation failed from server encoding to wchar_t