Fri Aug 20 15:11:44 PDT 2010
- Previous message: [Slony1-general] Slony & Locking
- Next message: [Slony1-general] Slony & Locking
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
ChronicDB Community Team <community at chronicdb.com> writes: > We would welcome feedback in improving this solution, in adding more > features, and in making it more accessible to PostgreSQL users. More > technical details can be found at: > http://chronicdb.com/technical_strengths It's rather rude to side-track discussions on how to improve Slony-I on our mailing list. If you have suggestions as to how we might improve the locking behaviour of Slony-I in ways that may be included into our code and documentation, feel free to contribute. If, however, you're interested in making your proprietary solution more featureful, it is probably apropos to arrange to engage staff and/or consultants to work on that. -- select 'cbbrowne' || '@' || 'ca.afilias.info'; Christopher Browne "Bother," said Pooh, "Eeyore, ready two photon torpedoes and lock phasers on the Heffalump, Piglet, meet me in transporter room three"
- Previous message: [Slony1-general] Slony & Locking
- Next message: [Slony1-general] Slony & Locking
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list