pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim C. Nasby <jnasby@pervasive.com>
To: Mark Liberman <mliberman@mixedsignals.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Feedback on auto-pruning approach
Date: Tue, 28 Mar 2006 12:19:03 -0600
Message-ID: <20060328181903.GU75181@pervasive.com> (raw)
In-Reply-To: <9D938282F8C6EE43B748B910386DE93E0138B418@srvgpimail1.GPI.local>
References: <9D938282F8C6EE43B748B910386DE93E0138B418@srvgpimail1.GPI.local>

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 whichever threshold 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 db size limit to be as large as possible - how much disk space should I reserve for standard Postgres operations - e.g. sort space, WAL, etc..  I'm sure this depends a bit on our configuration, etc.. but if someone can point me in the direction as 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



view thread (9+ messages)  latest in thread

Message-ID: <20060328181903.GU75181@pervasive.com>
Permalink:  ../20060328181903.GU75181@pervasive.com/
Also on:    postgresql.org/message-id/20060328181903.GU75181@pervasive.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: jnasby@pervasive.com, mliberman@mixedsignals.com
  Subject: Re: Feedback on auto-pruning approach
  In-Reply-To: <20060328181903.GU75181@pervasive.com>
  References: <9D938282F8C6EE43B748B910386DE93E0138B418@srvgpimail1.GPI.local> <20060328181903.GU75181@pervasive.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox