Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <gnanam@zoniac.com>) id 1Tb6VM-0005uG-3Q
	for pgsql-admin@postgresql.org; Wed, 21 Nov 2012 09:22:00 +0000
Received: from rs133.luxsci.com ([72.32.115.26])
	by magus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <gnanam@zoniac.com>) id 1Tb6VH-0000fg-Ia
	for pgsql-admin@postgresql.org; Wed, 21 Nov 2012 09:21:59 +0000
Received: from GNANAM (NSG-Static-009.236.71.182.airtel.in [182.71.236.9] (may
	be forged)) (authenticated bits=0)
	by rs133.luxsci.com (8.13.8/8.13.8) with ESMTP id qAL9LmpH021834;
	Wed, 21 Nov 2012 03:21:51 -0600
Reply-To: <gnanam@zoniac.com>
From: "Gnanakumar" <gnanam@zoniac.com>
To: <pgsql-admin@postgresql.org>
Subject: Database archive solutions
Date: Wed, 21 Nov 2012 14:51:51 +0530
Organization: Zoniac Software Private  Limited
Message-ID: <014101cdc7c9$a73bcb00$f5b36100$@zoniac.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
thread-index: Ac3HyT3ROPQ4GdiUSWCxFXpj4/kZLw==
Content-Language: en-us
X-Lux-Comment: Message qAL9LmpH021834 sent by user #22393
X-Pg-Spam-Score: 0.1 (/)
X-Archive-Number: 201211/112
X-Sequence-Number: 40357

Hi,

Our application requirement demands archiving of records, so that
performance/speed of the application is not compromised.  So, am looking
out/evaluating on various techniques/solutions available for database
archiving, in general, for PostgreSQL.

Few solutions that comes to my mind are:

    1) Table partitioning
    2) Separate tablespace and/or schema
    3) Moving archived records/tables to a different harddisk

Any other suggestions/pointers/solutions are really welcome and appreciated.

NOTE: We're running PostgreSQL v9.1.3 on CentOS5.2

Regards,
Gnanam