fix: skipping vacuum inside explicit transaction

[dantengsky]

I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/

Summary

Skipping vacuum inside explicit transaction

Tests

• Unit Test
• Logic Test
• Benchmark Test
• No Test - Explain why

Type of change

• Bug Fix (non-breaking change which fixes an issue)
• New Feature (non-breaking change which adds functionality)
• Breaking Change (fix or feature that could cause existing functionality not to work as expected)
• Documentation Update
• Refactoring
• Performance Improvement
• Other (please describe):

---

This change is 

[github-actions]

🤖 Smart Auto-retry Analysis

Workflow Run: 15825768808

The workflow run has been analyzed for retryable errors using job annotations.

---

📊 Analysis Summary

Metric	Count
Total Failed/Cancelled Jobs	2
Jobs with Retryable Errors	2
Jobs with Code/Test Issues	0

✅ Retry Status: AUTOMATIC RETRY INITIATED

2 job(s) have been automatically retried due to infrastructure issues detected in annotations:

• Runner communication failures
• Network timeouts
• Resource exhaustion
• Other transient infrastructure problems

📈 Monitor Progress: View in Actions

---

🔍 Detailed Job Analysis

🔄 linux / test_unit

Status: ✅ Retryable (Infrastructure Issue)
Reason: Infrastructure issue detected
Annotations: 1 found

🔄 linux / build (x86_64, X64)

Status: ✅ Retryable (Infrastructure Issue)
Reason: Infrastructure issue detected
Annotations: 1 found

---

🤖 About This Analysis

This is an automated analysis and retry triggered by the smart retry workflow using job annotations. The system analyzes failure patterns to distinguish between:

• 🔄 Infrastructure Issues: Runner failures, network timeouts, resource exhaustion
• ❌ Code/Test Issues: Compilation errors, test failures, logic problems

Only infrastructure issues are automatically retried to avoid wasting resources on code problems that need manual fixes.

[github-actions]

🤖 Smart Auto-retry Analysis

Workflow Run: 15825768808

The workflow run has been analyzed for retryable errors using job annotations.

---

📊 Analysis Summary

Metric	Count
Total Failed/Cancelled Jobs	1
Jobs with Retryable Errors	1
Jobs with Code/Test Issues	0

✅ Retry Status: AUTOMATIC RETRY INITIATED

1 job(s) have been automatically retried due to infrastructure issues detected in annotations:

• Runner communication failures
• Network timeouts
• Resource exhaustion
• Other transient infrastructure problems

📈 Monitor Progress: View in Actions

---

🔍 Detailed Job Analysis

🔄 linux / build (x86_64, X64)

Status: ✅ Retryable (Infrastructure Issue)
Reason: Infrastructure issue detected
Annotations: 1 found

---

🤖 About This Analysis

This is an automated analysis and retry triggered by the smart retry workflow using job annotations. The system analyzes failure patterns to distinguish between:

• 🔄 Infrastructure Issues: Runner failures, network timeouts, resource exhaustion
• ❌ Code/Test Issues: Compilation errors, test failures, logic problems

Only infrastructure issues are automatically retried to avoid wasting resources on code problems that need manual fixes.