Help Center/ TaurusDB/ Kernels/ Common Kernel Functions/ Idle Transaction Disconnection/ Function

Updated on 2024-12-23 GMT+08:00

View PDF

Function

If an idle transaction is not committed for a long time, its rollback will consume database resources and performance. If a large number of idle transactions are not committed and not rolled back for a long time, the performance loss to a database is severe especially during peak hours. GaussDB(for MySQL) can proactively terminate idle transactions. Different parameters are used to control different types of transactions. When idle transactions timed out, they are automatically rolled back and disconnected.

This function is supported when the kernel version is 2.0.39.230300 or later.

Parent topic: Idle Transaction Disconnection

Previous topic: Idle Transaction Disconnection

Next topic: Parameter Description

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.