I created a range partition on an existing table of size around 4G using create_range_partitions with partition_data set to false.
After that I ran partition_table_concurrently. After the data migration has been completed (which I verified by running SELECT * FROM pathman_concurrent_part_tasks;), the parent table size still remains 4G.
Does this mean that parent table still contains all data? Similar question about indexes on parent table, our indexes on parent table are still huge in size. Should I manually clean the parent table and indexes?