If I run create_range_partitions and then partition_table_concurrently at a later time, then how is the query plan generated for all the queries that happen in between?
I ran explain on a query and the query plan showed that ti would read data from the child, even though the data migration was not complete.
Ideally all the queries should be executed on parent till the data migration is complete. After migration, query should execute only on children.
Documentation of partition_table_concurrently is not very clear on this.