The docs claim that the master table “should” be empty. It it possible to just 
create child tables off an existing master table with data, then just inserting 
data into the new child tables.

THe plan would be to keep data in the master table and purge it over time until 
it’s eventually empty, then drop the indexes as well.

Fully understanding that data needs to be placed in the right child tables. 
Data outside of those child ranges would remain as “old data” in the master 

Just trying to grab if that’s an acceptable migration of live data from a 
single large table and move into partitioning. Think of it as a very large 
table of cyclic data that ages out. New data in child tables while removing 
data from the master table over time.


Reply via email to