Distributed Table Partitioning

From: Leonardo M(dot) Ramé <l(dot)rame(at)griensu(dot)com>
To: PostgreSql-general <pgsql-general(at)postgresql(dot)org>
Subject: Distributed Table Partitioning
Date: 2016-03-13 01:25:01
Message-ID: 56E4C16D.6010807@griensu.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I have this problem: a Master table containing records with a timestamp
column registering creation date-time, and one Detail table containing
info related to the Master table.

As time went by, those tables grew enormously, and I can't afford
expanding my SSD VPS. So I'm thinking about storing only NEW data into
it, and move OLD data to a cheaper SATA VPS.

The goal is using the SSD server as "main", and the other (or others?)
as "child", so queries still go to the main server, it somehow detects
which records must be fetched from it and what from the child servers,
then return the "composed" dataset to the caller.

I think this is called Distributed Horizontal Table Partitioning.

Is there a way to do this without changing my application code?.

Regards,
--
Leonardo M. Ramé
Medical IT - Griensu S.A.
Av. Colón 636 - Piso 8 Of. A
X5000EPT -- Córdoba
Tel.: +54(351)4246924 +54(351)4247788 +54(351)4247979 int. 19
Cel.: +54 9 (011) 40871877

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alvaro Aguayo Garcia-Rada 2016-03-13 01:33:59 Re: Distributed Table Partitioning
Previous Message Karsten Hilbert 2016-03-13 01:03:15 Re: pg_restore fails