I think that the first thing that you need to decide is where your bottleneck is (if there's any).
You can have one single PostgreSQL server and many tinyerp-servers running against the same database. That's pretty straight forward. You can even use some sort of load balancer in front of them if needed. If you have concerns about the availability of the database you can replicate it with many different systems: - Slony is easy if you just need to have a slave with take over capabilities in case of failure - If you need some sort of database cluster you can use PGPoolII. With it you can have one master and severral syncronized slaves. This setup allows you to send INSERT, UPDATE, DELETE queries to the master and SELECTs to any of the slaves, thus reducing the database load. - Postgres-R recently released provides a multi-master database solution for postgres but it is somehow difficult to set up and configure.. Regards, Pedro _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
