I have a table currently that adds up all the parts I have used to make products. I have a qty figure in there and I sum that. However the problem is at the moment I have to consume qtys of parts each time I build a product, but i would prefer to consume the parts 1 at a time. That would create many more records so I would need to sum a much larger data set to make that work because instead of a qty of 100 parts consumed, there would not be 100 separate records. But it would me closer to whats happening when I build products so it would be better from an operations point of view.
How many records can PosgreSQL sum without slowing down? I could wind up with millions of records if I use a separate record for each one.
Only one software tool needs those summaries, but it has to do it at launch, so the longer the sum takes the longer the tool will take to launch. I have a few thousand part types as well so I am doing a sum for each part type.
Grant
|