During the AWS summary line item table population, we currently employ a common table expression in Trino to remove all tag keys that are not enabled. This filtering occurs when reading from Trino to populate our Postgres table.

However, in the case of our other cloud providers, a divergence exists in our summary process. After the initial insertion into Postgres, we invoke an update_line_item_daily_summary_with_enabled_tags function, updates the tag columns to only include the enabled tag keys. 

This issue pertains to standardizing our approach across all cloud providers by transitioning them to filter out disabled keys in Trino during the insertion process into PostgreSQL, aligning with the methodology applied for AWS.