Vacuum Full Verbose did not get the disk space back to OS, it did bloat my
indexes, also got out of memory error. I dumped the suspicious table,
deleted it, re-created it, then restored the data and re-indexed the data,
so I got the disk space back.
To avoid the database eating up the disk space again, I have adjusted the
autovacuum parameters, to make it keep up with the updates.
Not sure if this is the right way to solve this kind of problem.
From: Ben Chobot [mailto:bench(at)silentmedia(dot)com]
Sent: 17 February 2010 13:34
To: Rose Zhou
Subject: Re: [PERFORM] disk space usage unexpected
On Feb 15, 2010, at 1:25 PM, Rose Zhou wrote:
I will adjust the auto vacuum parameters. It is on now, maybe not frequently
How to get the disk space back to OS? Will a Vacuum Full Verbose get the
disk space back to OS?
Yes, but it might bloat your indexes. Do you actually need to get your disk
space back? If you did, would the database just eat it up again after more
In response to
pgsql-performance by date
|Next:||From: Brad Nicholson||Date: 2010-02-17 19:01:16|
|Subject: Re: bgwriter tunables vs pg_stat_bgwriter|
|Previous:||From: Ben Chobot||Date: 2010-02-17 18:34:17|
|Subject: Re: disk space usage unexpected|