network profile
| bio | website | |
|---|---|---|
| location | Thailand | |
| age | ||
| visits | member for | 7 months |
| seen | Dec 23 '12 at 20:03 | |
| stats | profile views | 2 |
|
Nov 17 |
answered | Teaching Slony replication to select slave nodes |
|
Oct 4 |
comment |
Teaching Slony replication to select slave nodes Materialized view? Seems we'll duplicate our data plus additional overhead in maintaining it with triggers. On top of it it's difficult to trace errors in triggers because they do not interrupt update transactions that start them. I'm not sure the system in question allows it. I'm beginning to think more in the direction of hacking Slon source code somehow, like bounce ins/updates on slave if new row violates integrity check. Or maybe use a different replication engine? I hear xDB Enterprise has some sort of "row filter". |
|
Oct 4 |
awarded | Student |
|
Oct 4 |
asked | Teaching Slony replication to select slave nodes |
