I need to create a Postgres table partitioned by range. The partitioning approach is essential because the table will need to store large volumes of data and be queried frequently. The plan is to set up a job that periodically drops old, unused partitions.

My backend is in Rails (version 7.2). I know that partitioning support was tricky before due to ActiveRecord's lack of support for composite primary keys, but my understanding is that this was addressed in Rails 7. However, I'm still a bit unsure how to go about implementing this.

All the examples I've found so far are for previous versions of Rails, where people used workarounds, such as:

• Creating a partitioned table without a primary key and monkey-patching ActiveRecord to make the save and update functions work, or
• Creating a partitioned table with a primary key on the id column and a composite index on both the id and the partition key.

How do I create a new partitioned table leveraging Rails 7's support for composite primary keys?