pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <scott.marlowe@gmail.com>
To: chambers@imageworks.com
Cc: pgsql-performance@postgresql.org
Subject: Re: db performance/design question
Date: Wed, 12 Sep 2007 16:58:34 -0500
Message-ID: <dcc563d10709121458y2d8b921etb629aae32a59be3b@mail.gmail.com> (raw)
In-Reply-To: <46E84D15.8020600@imageworks.com>
References: <46E84D15.8020600@imageworks.com>

On 9/12/07, Matt Chambers <chambers@imageworks.com> wrote:
>
>
>  I'm designing a system that will be doing over a million inserts/deletes on
> a single table every hour.  Rather than using a single table, it is possible
> for me to partition the data into multiple tables if I wanted to, which
> would be nice because I can just truncate them when I don't need them.  I
> could even use table spaces to split the IO load over multiple filers.  The
> application does not require all this data be in the same table.   The data
> is fairly temporary, it might last 5 seconds, it might last 2 days, but it
> will all be deleted eventually and different data will be created.
>
>  Considering a single table would grow to 10mil+ rows at max, and this
> machine will sustain about 25mbps of insert/update/delete traffic 24/7 -
> 365, will I be saving much by partitioning data like that?

This is the exact kind of application for which partitioning shines,
especially if you can do the inserts directly to the partitions
without having to create rules or triggers to handle it.  If you have
to point at the master table, stick to triggers as they're much more
efficient at slinging data to various sub tables.



view thread (2+ messages)

Message-ID: <dcc563d10709121458y2d8b921etb629aae32a59be3b@mail.gmail.com>
Permalink:  ../dcc563d10709121458y2d8b921etb629aae32a59be3b@mail.gmail.com/
Also on:    postgresql.org/message-id/dcc563d10709121458y2d8b921etb629aae32a59be3b@mail.gmail.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-performance@postgresql.org
  Cc: scott.marlowe@gmail.com, chambers@imageworks.com
  Subject: Re: db performance/design question
  In-Reply-To: <dcc563d10709121458y2d8b921etb629aae32a59be3b@mail.gmail.com>
  References: <46E84D15.8020600@imageworks.com> <dcc563d10709121458y2d8b921etb629aae32a59be3b@mail.gmail.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