Tue Dec 12 09:48:16 PST 2006
- Previous message: [Slony1-general] Is Slony 1.2.stable compatible with postgreSQl 8.2?
- Next message: [Slony1-general] question about potential problems
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
hi, first: i'm using slony 1.1.5 on linux on quite busy database. i know that the correct way to add field to table is to do it using execute script. but. this is cumbersome (requires lock, blocks database). i am using this method: add column on slave and (very quickly, but a bit later) - add column on master. now. i know that it is not good. i saw that at lease definitions of triggers differ. but - this is way faster. question is - what is the worst case scenario? what should happen for me to get punished for this? as for now - even with bad (kvvvv instead of kvvvvv) triggers i still get good results (kudos to dev team). is it safe but not sugested, or there is some scenario which could lead to something bad? if yes, then what scenario and what bad? best regards, depesz -- http://www.depesz.com/ - nowy, lepszy depesz -------------- next part -------------- An HTML attachment was scrubbed... URL: http://gborg.postgresql.org/pipermail/slony1-general/attachments/20061212/3a8f0744/attachment.html
- Previous message: [Slony1-general] Is Slony 1.2.stable compatible with postgreSQl 8.2?
- Next message: [Slony1-general] question about potential problems
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list