Partitioning: Initial suggestion

[m0rt3nlund]

Hi!

This is my initial suggestion to include "partitioning" support.
Feedback is appreciated!

Contributor checklist

• Bug fixes include regression tests
• Features include unit/acceptance tests

[zachdaniel]

The general pattern looks good, although there will be some details to talk through and some docs about how to manage partitions, maybe some builtin changes to do it automatically etc. The migration generator is going to have to have some kind of handling for changing the partition strategy as well.

I noticed some unfinished bits as well, i.e for creating range partitions. We should definitely avoid the string interpolation in the SQL there as well.

[m0rt3nlund]

I made some updates before reading your comments.
I will try to make a new draft considering your comments :)

[m0rt3nlund]

Also found some problems when updating the primary key on multitenancy resource.
Not sure it this is how you would prefer to fix it.

[zachdaniel]

Could we separate out that other fix that you mentioned into its own PR so that I can review in isolation?

[rgraff]

Didn't see this PR until just now, but I have a partitioning solution here that I extracted out my app.
#664

My solution is more generalized adding create_table_options and then documentation on how you can do partitioning.

[m0rt3nlund]

Closing this pull-request as I made an extension that uses the latest added create_table_options instead

https://hex.pm/packages/ash_postgres_partition