Re: partial VACUUM FULL - Mailing list pgsql-general

From Bill Moran
Subject Re: partial VACUUM FULL
Date
Msg-id 4060C30D.3030106@potentialtech.com
Whole thread Raw
In response to Re: partial VACUUM FULL  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: partial VACUUM FULL
List pgsql-general
Tom Lane wrote:
>>Another
>>is that the setting of vacuum_mem (in postgresql.conf) limits the amount of
>>cleanup that vacuum can do.
>
> This is completely untrue.  Increasing vacuum_mem will likely make
> things faster on large tables (by avoiding the need for multiple passes
> over the indexes).  It will not change the end result though.

My mistake then.

Was this true for some previous version?  I could have swore I read somewhere
that vacuum_mem had to be set high enough or vacuum wouldn't be able to clean
everything up (aside from anything locked in transactions).  Now that I'm
looking, I can't find any such reference, so perhaps I misunderstood and
twisted the meaning.

Is performance the only reason for increasing vacuum_mem?

--
Bill Moran
Potential Technologies
http://www.potentialtech.com


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: partial VACUUM FULL
Next
From: Tom Lane
Date:
Subject: Re: partial VACUUM FULL