It is worth noting here that most of the problems listed here for active discussion are problems that occur with volume and load.
But for reference:
1. Table partitioning was used to solve autovacuum and statistical correlation problems on the work tables
2. Non-1NF designs need to understand atomicity as being relational and not ontological in nature. I.e. what you are doing with the data determines atomicity far more than the data itself, and
3. Immutable functions and functional indexes rock on PostgreSQL.
Also I cannot stress enough the need for doing real monitoring and simulation of problems.
4 comments
[ 0.22 ms ] story [ 18.6 ms ] threadBut for reference:
1. Table partitioning was used to solve autovacuum and statistical correlation problems on the work tables
2. Non-1NF designs need to understand atomicity as being relational and not ontological in nature. I.e. what you are doing with the data determines atomicity far more than the data itself, and
3. Immutable functions and functional indexes rock on PostgreSQL.
Also I cannot stress enough the need for doing real monitoring and simulation of problems.
https://lists.postgresql.org/mj/mj_wwwusr?user=&passw=&func=...