Wed Nov 29 11:23:42 PST 2006
- Previous message: [Slony1-general] Porting slony to allow oracle to be master (no slave required)
- Next message: [Slony1-general] Porting slony to allow oracle to be master (no slave required)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
* Csaba Nagy <nagy at ecircle-ag.com> [061129 18:05]: > Well, given that slony is messing with all the constraint/foreign > key/index stuff in very postgres DB specific way on the slave so That's the easy stuff. It basically disables triggers in a voodoo way that messes up the schema. (the foreign key effects come from this.) > obviously that even me who does not know too much about slony internals > am aware of it, I'm pretty sure the slave part is the harder one to > implement... I mean more work. Not to mention we don't need that right The harder part is capturing data, especially in a sane and transactionally safe way. > now... so for me a step by step thing with enabling master first would > be better. > Andreas
- Previous message: [Slony1-general] Porting slony to allow oracle to be master (no slave required)
- Next message: [Slony1-general] Porting slony to allow oracle to be master (no slave required)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list