fix: Boundary checks for maxStandardError in APPROX_COUNT_DISTINCT.

Author: FearfulTomcat27

integration-test/src/test/java/org/apache/iotdb/relational/it/query/recent/IoTDBTableAggregationIT.java

@@ -4157,6 +4157,12 @@ public void approxCountDistinctTest() {
         new String[] {"time", "province", "_col2", "_col3"},
         retArray,
         DATABASE_NAME);
+
+    tableResultSetEqualTest(
+        "select approx_count_distinct(time,0.0040625),approx_count_distinct(time,0.26) from table1",
+        new String[] {"_col0", "_col1"},
+        new String[] {"10,11,"},
+        DATABASE_NAME);
   }
 
   @Test

iotdb-core/datanode/src/main/java/org/apache/iotdb/db/queryengine/execution/operator/source/relational/aggregation/HyperLogLog.java

@@ -105,8 +105,8 @@ private static int indexBitLength(int numberOfBuckets) {
   }
 
   private static int standardErrorToBuckets(double maxStandardError) {
-    if (maxStandardError <= LOWEST_MAX_STANDARD_ERROR
-        || maxStandardError >= HIGHEST_MAX_STANDARD_ERROR) {
+    if (maxStandardError < LOWEST_MAX_STANDARD_ERROR
+        || maxStandardError > HIGHEST_MAX_STANDARD_ERROR) {
       throw new IoTDBRuntimeException(
           String.format(
               "Max Standard Error must be in [%s, %s]: %s",