[bug] tae: fix hang issue and reserve some table IDs.

[volgariver6]

What type of PR is this?

• API-change
• BUG
• Improvement
• Documentation
• Feature
• Test and CI
• Code Refactoring

Which issue(s) this PR fixes:

issue https://github.com/matrixorigin/MO-Cloud/issues/2995

What this PR does / why we need it:

fix hang issue and reserve some table IDs.

[matrix-meow]

@volgariver6 Thanks for your contributions!

Pull Request Review:

Title:

The title of the pull request clearly indicates that it is addressing a bug related to fixing a hang issue and reserving some table IDs.

Body:

The body of the pull request provides information on the type of PR (BUG), the specific issue being fixed (issue #2995), and the purpose of the PR which is to fix the hang issue and reserve table IDs.

Changes:

1. In types.go:

   • Added a constant MO_RESERVED_MAX with a value of 100 to represent the maximum reserved table ID.

2. In database.go:

   • Added a check in CreateTableEntryWithTableId function to ensure that the provided table ID is not within the reserved range (less than MO_RESERVED_MAX).
   • This change prevents the creation of a table with a reserved ID, returning an error if the ID falls within the reserved range.

Suggestions for Improvement:

1. Optimization:

   • Consider consolidating the e.Lock() and defer e.Unlock() statements in the CreateTableEntry and CreateTableEntryWithTableId functions to avoid repetitive code and ensure proper locking and unlocking in a consistent manner.

2. Error Handling:

   • It's good to check for reserved table IDs, but consider providing a more descriptive error message when rejecting a table creation due to a reserved ID. Include information on why the ID is reserved and suggest an alternative approach.

3. Consistency:

   • Ensure consistent use of error handling and locking mechanisms throughout the codebase to maintain clarity and reliability.

4. Security:

   • While the changes made in this PR do not introduce any obvious security vulnerabilities, it's essential to regularly review and update security measures in the codebase to prevent potential security risks.

By addressing the suggestions provided above, the codebase can be optimized for better performance, maintainability, and clarity. Additionally, maintaining a focus on security best practices will help ensure the overall integrity of the system.