Is it possible to return immediately when running long-running DDL or DML?

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: 跑耗时长的ddl或dml时能否直接返回

| username: Qiuchi

A possibly common-sense question… For example, when I run DDL or DML like batch limit 1000 delete …, it takes a long time to complete. Previously, I could only run it and then disconnect, then open a new connection. Is there any way to let the SQL return completion directly but continue executing in the background?

| username: liuis | Original post link

Why doesn’t the program return directly and let the task continue running?

| username: Qiuchi | Original post link

Because it’s not a program…

| username: h5n1 | Original post link

You can post a feedback thread.

| username: liuis | Original post link

This kind of thing can also be implemented at the underlying level, by starting a goroutine in the background to run tasks.

| username: h5n1 | Original post link

Provide feedback, official evaluation, scheduling. Previously, I also suggested that batch DML should support concurrent execution of subtasks.

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.