Keith Fiske

So, the error for maintenance not being able to create a partition should hopefully happen well before "today" and would mean that your application inserted data further into the future...

Just checking to see if you're still having any issues with partitioning data out of the default

Changing this to be marked as Feature Request due to seeing about adding a mode to `partition_data_proc()` so that it can work in batches.

This is going to require a bigger re-design than I can do at the moment, so setting for 5.x redesign milestone. Currently the temp table is set to `ON COMMIT...

Are you saying the partition configuration already exists in pg_partman? If that's the case, you'll probably need something that first checks the `part_config` table to see if it has an...

It looks like you can control this yourself currently by setting [default_table_access_method](https://www.postgresql.org/docs/14/runtime-config-client.html#GUC-DEFAULT-TABLE-ACCESS-METHOD), which is a user/session level setting you can change at anytime without any special permissions needed.

I don't have a means of doing that currently with the background worker. I'll change this issue into a feature request to see if something like that is possible, but...

So there actually is a way to do this now, but may or may not work for you. You can currently set which user runs the partman maintenance via a...

If you need the primary keys to be created on the child tables from the moment that `create_parent()` is called, then you will have to precreate your template table, add...

Thanks for the long time support and usage! I had not planned on adding hash partitioning support to pg_partman. Mostly because the decision on the hash size has to be...