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:32:28 -0600
Message-ID: <20060328183228.GV75181@pervasive.com> (raw)
In-Reply-To: <9D938282F8C6EE43B748B910386DE93E0138B41A@srvgpimail1.GPI.local>
References: <9D938282F8C6EE43B748B910386DE93E0138B41A@srvgpimail1.GPI.local>

On Tue, Mar 28, 2006 at 10:23:45AM -0800, Mark Liberman wrote:
> > Probably your biggest issue will be temporary files created by temporary tables, sorts that spill to disk, etc.
> 
> Is there any way to monitor this so I can estimate?

Keep an eye on $PGDATA/base/{database_oid}/pgsql_tmp.

> > What I'm confused by is the concern about disk space in the first place.
> 
> We provide a device to customers that must run in an unattended fashion for as long as the hardward holds up.  So, regardless of the disk size, they will run out at some time.  Some of our solutions grow by 3.5 Gigs per day - and 6 months of history is not an unreasonable expectation.  We've just decided we want to keep as much history as possible given space limitations.

You might want to take a look at http://rrs.decibel.org, which is
something I created for a similar purpose.
-- 
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: <20060328183228.GV75181@pervasive.com>
Permalink:  ../20060328183228.GV75181@pervasive.com/
Also on:    postgresql.org/message-id/20060328183228.GV75181@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: <20060328183228.GV75181@pervasive.com>
  References: <9D938282F8C6EE43B748B910386DE93E0138B41A@srvgpimail1.GPI.local> <20060328183228.GV75181@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