NOTE:

• Since the nightly tally query currently depends on the bucket/cores rows, we will need to update the query to join on the measurements tables for these values.
• Also, this runs the risk of performance challenges, engaging the performance team for nightly tally main branch vs feature branch for this capability before merge. This can also be investigated with local testing via jprofiler/ postgres explain plan, etc. before engaging the performance team. 
• If something gnarly comes up from the performance investigation, pause and bring back to team to decide on course of action, use your best judgement. 
• Consider database index changes, other work necessary to ensure performant results. 

QE: This will require regression testing on the nightly tally.