Skip site navigation (1) Skip section navigation (2)

Re: disk space usage unexpected

From: "Rose Zhou" <rose(at)anatec(dot)com>
To: "'Ben Chobot'" <bench(at)silentmedia(dot)com>
Cc: <pgsql-performance(at)postgresql(dot)org>
Subject: Re: disk space usage unexpected
Date: 2010-02-17 18:43:46
Message-ID: 8FCC635F9E0B4F618FFCA91388EAB4B1@Cicero (view raw or flat)
Thread:
Lists: pgsql-performance
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.
 



Best Regards

Rose Zhou 

 


  _____  

From: Ben Chobot [mailto:bench(at)silentmedia(dot)com] 
Sent: 17 February 2010 13:34
To: Rose Zhou
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: [PERFORM] disk space usage unexpected


On Feb 15, 2010, at 1:25 PM, Rose Zhou wrote:


Thanks Ben:
 
I will adjust the auto vacuum parameters. It is on now, maybe not frequently
enough.
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
activity?

In response to

pgsql-performance by date

Next:From: Brad NicholsonDate: 2010-02-17 19:01:16
Subject: Re: bgwriter tunables vs pg_stat_bgwriter
Previous:From: Ben ChobotDate: 2010-02-17 18:34:17
Subject: Re: disk space usage unexpected

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group