I guess that would work if you used a view to combine both tables, but you
would still need a BEFORE trigger to make sure DML goes to the appropriate
table.
Another solution might be to use dblink if you need to access the SATA
table on the 2nd VPS,
On Sun, Mar 13, 2016 at 11:37 AM, Leonardo M. Ra
El 13/03/16 a las 10:04, Peter J. Holzer escribió:
On 2016-03-12 21:19:11 -0500, Melvin Davidson wrote:
- Original Message -
From: "Leonardo M. Ramé"
To: "PostgreSql-general"
Sent: Saturday, 12 March, 2016 8:25:01 PM
Subject: [GENERAL] Distributed Table Partiti
On 2016-03-12 21:19:11 -0500, Melvin Davidson wrote:
> - Original Message -
> From: "Leonardo M. Ramé"
> To: "PostgreSql-general"
> Sent: Saturday, 12 March, 2016 8:25:01 PM
> Subject: [GENERAL] Distributed Table Partitioning
>
> I have this problem: a Master tabl
oops! Better example
eg: {note: below is psuedo code}
child {master} (SSD) NO ROWS33
tg_insert_child before insert execute tgf_split_data
child1 (SSD) CONSTRAINT timestamp > {specified time}
child2 (SATA) CONSTRAINT timestamp <= {specified time}
tgf_split_data()
On Sat, Mar 12, 2016 at 8:33 PM, Alvaro Aguayo Garcia-Rada <
aagu...@opensysperu.com> wrote:
> Hi. I think pgpool-II can do that job for you. It's a middleware, so you
> can use it without even changing your app code(but your postgres
> configuration). It suppoerts many clustering functions, inclu
Hi. I think pgpool-II can do that job for you. It's a middleware, so you can
use it without even changing your app code(but your postgres configuration). It
suppoerts many clustering functions, including replication, failover, and a lot
more; it also supports partitioning. so that may be suitabl
