pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Michal Merta <michal.merta@greycortex.com>
To: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Amount of unused space on a storage device
Date: Thu, 31 Aug 2017 16:52:05 +0200
Message-ID: <37bd3391-30db-292c-0cf9-110860461b0d@greycortex.com> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

Hello everyone,

We have an OLAP database on dedicated RAID storage with a total capacity 
of 100TB. The transaction log and temp_tablespace are stored on a 
separated drive.
All tables are partitioned by timestamp of insert, the size of each 
partition is 1 week. All tables are insert only, no update or delete 
ever occurs. The amount of data stored peer week is ~1TB.

We use following maintenance algorithm:
   IF amount of free space on storage is lower than BOUNDARY, THEN
     backup all partitions for oldest week
     drop these partitions from database

Our desired behavior is to keep as much data as possible in database for 
analytical queries.

My question is:
Having 100TB capacity and data coming in at a fixed rate of ~1TB per 
week, what would be an optimal BOUNDARY? Or to put it another way, what 
is a reasonable amount of unused space on a storage device of this size?

Thanks & Regards,
Michal Merta

Message-ID: <37bd3391-30db-292c-0cf9-110860461b0d@greycortex.com>
Permalink:  ../37bd3391-30db-292c-0cf9-110860461b0d@greycortex.com/
Also on:    postgresql.org/message-id/37bd3391-30db-292c-0cf9-110860461b0d@greycortex.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 using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: michal.merta@greycortex.com
  Subject: Re: Amount of unused space on a storage device
  In-Reply-To: <37bd3391-30db-292c-0cf9-110860461b0d@greycortex.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