Partman CALL public.partition_data_proc(); cancelled. #741
Replies: 2 comments
-
Since you're using the procedure, all the work that is done each loop is committed. So in your case, the rows copied by those first 3 loops should have been partitioned out and removed from the default and stay like that if it's cancelled. The only thing that will rollback if you cancel it is the work that has been done on the current partition that it is working on. There is no chance of data corruption or loss due to this process alone. All uncommitted row changes and the rows that have not yet been moved will remain in the default. |
Beta Was this translation helpful? Give feedback.
-
Moving this to a discussion. |
Beta Was this translation helpful? Give feedback.
-
Hi Keith,
I have a partman monthly partition table with 100Million records in that 50M records are in defatult partition, to distribute the data in particular partitions i have triggered CALL public.partition_data_proc('test.order_info');
NOTICE: Loop: 1, Rows moved: 8401488
NOTICE: Loop: 2, Rows moved: 8006831
NOTICE: Loop: 3, Rows moved: 8405148. ----- it copied around 24M records in particular 3 month partitions.
Due to some reason if I cancel/kill the procedure in between what will be going to happen ?
will it revoke all copied rows into default partition ?
Any chance for data corruption ?
if data already copied to respective partitions what will happen for remaining 26M records which are present in default partition.
Thanks,
Santoshkumar
Beta Was this translation helpful? Give feedback.
All reactions