On Mon, Mar 27, 2006 at 06:32:42PM -0800, Mark Liberman wrote:
> So, I have finally complete this auto-pruning solution. It has proven effective in keeping the size of the db under
whicheverthreshold I set in an unattended fashion.
>
> I have one final question. If my goal is to maximize the amount of historical data that we can keep - e.g. set the
dbsize limit to be as large as possible - how much disk space should I reserve for standard Postgres operations - e.g.
sortspace, WAL, etc.. I'm sure this depends a bit on our configuration, etc.. but if someone can point me in the
directionas to what factors I should consider, I'd greatly appreciate it.
Probably your biggest issue will be temporary files created by temporary
tables, sorts that spill to disk, etc.
What I'm confused by is the concern about disk space in the first place.
Drives are very cheap, people are normally much more concerned about IO
bandwidth.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
