pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Mario Splivalo <mario.splivalo@megafon.hr>
To: Igor Neyman <ineyman@perceptron.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Live sort-of-'warehousing' database how-to?
Date: Thu, 01 Apr 2010 09:54:37 +0200
Message-ID: <4BB4513D.7000705@megafon.hr> (raw)
In-Reply-To: <F4C27E77F7A33E4CA98C19A9DC6722A205C1872B@EXCHANGE.corp.perceptron.com>
References: <4BB35A02.5060100@megafon.hr>
	<F4C27E77F7A33E4CA98C19A9DC6722A205C1872B@EXCHANGE.corp.perceptron.com>

Igor Neyman wrote:
> 
> Partition your MESSAGES table by week or month  (read on table
> partitioning in PG docs).
> 
> Pg_dump "old" purtitions from "current" server, when they are not needed
> any more.
> Move backups of dumped partitions to your "auxilary" server, and
> pg_restore them there.

Hm. I never actually wanted to use partitioning (and I always thought my
databases are small in size and don't need partitioning) because of what
seems to be awful overhead of maintaining insert rules or insert
triggers. But your idea sound plausible for exactly what i need.
The only problem is that on the "auxiliary" server I wouldn't have the
last month/week or so, and I'd love to so every day or maybe every hour.
Will see, thank you! :)

	Mike





view thread (3+ messages)

Message-ID: <4BB4513D.7000705@megafon.hr>
Permalink:  ../4BB4513D.7000705@megafon.hr/
Also on:    postgresql.org/message-id/4BB4513D.7000705@megafon.hr

 · 

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: mario.splivalo@megafon.hr, ineyman@perceptron.com
  Subject: Re: Live sort-of-'warehousing' database how-to?
  In-Reply-To: <4BB4513D.7000705@megafon.hr>

* 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