I'm building a PostgreSQL database with the intent to host modelisation results for different projects.
Each project has a set of receptors points (~5000-10000 receptors) and have many results sets (could be as much as 100 000 results sets (here called scenarios results)).
The problem with this design is that the table receptor_results is going to be extremely heavy. For a project with 5000 receptors and 50 000 scenarios, it will generate 250 000 000 rows!
Any suggestion on how I can avoid such thing ?