fix: Correct PostgreSQL accelerator connection pool parameter name and defaults

The docs listed pg_connection_pool_min_idle (default 1) and connection_pool_size
(default 5), but the code uses pg_connection_pool_min (default 5) and
connection_pool_size (default 10).

Author: Claude

website/docs/components/data-accelerators/postgres/index.md

@@ -34,8 +34,8 @@ The connection to PostgreSQL can be configured by providing the following `param
   - `prefer`: This mode will try to establish a secure TLS connection if possible, but will connect insecurely if the server does not support TLS.
   - `disable`: This mode will not attempt to use a TLS connection, even if the server supports it.
 - `pg_sslrootcert`: Optional parameter specifying the path to a custom PEM certificate that the connector will trust.
-- `pg_connection_pool_min_idle`: Optional. The minimum number of idle connections to keep open in the pool. Default is `1`.
-- `connection_pool_size`: Optional. The maximum number of connections to keep open in the connection pool. Default is `5`.
+- `pg_connection_pool_min`: Optional. The minimum number of connections to keep open in the pool, lazily created when requested. Default is `5`.
+- `connection_pool_size`: Optional. The maximum number of connections created in the connection pool. Default is `10`.
 
 Configuration `params` are provided in the `acceleration` section of a dataset.
 

website/versioned_docs/version-1.10.x/components/data-accelerators/postgres/index.md

@@ -34,8 +34,8 @@ The connection to PostgreSQL can be configured by providing the following `param
   - `prefer`: This mode will try to establish a secure TLS connection if possible, but will connect insecurely if the server does not support TLS.
   - `disable`: This mode will not attempt to use a TLS connection, even if the server supports it.
 - `pg_sslrootcert`: Optional parameter specifying the path to a custom PEM certificate that the connector will trust.
-- `pg_connection_pool_min_idle`: Optional. The minimum number of idle connections to keep open in the pool. Default is `1`.
-- `connection_pool_size`: Optional. The maximum number of connections to keep open in the connection pool. Default is `5`.
+- `pg_connection_pool_min`: Optional. The minimum number of connections to keep open in the pool, lazily created when requested. Default is `5`.
+- `connection_pool_size`: Optional. The maximum number of connections created in the connection pool. Default is `10`.
 
 Configuration `params` are provided either in the `acceleration` section of a dataset.
 

website/versioned_docs/version-1.10.x/components/data-connectors/mssql.md

@@ -12,7 +12,6 @@ The Microsoft SQL Server Data Connector enables federated/accelerated SQL querie
 
 1. The connector supports SQL Server authentication (SQL Login and Password) only.
 1. Spatial types (`geography`) are not supported, and columns with these types will be ignored.
-1. `DATETIME2` and `DATETIMEOFFSET` columns are mapped to Arrow `Timestamp(Nanosecond)`. Timestamps outside the nanosecond range (approximately years 1677–2262) will silently return `1970-01-01 UTC`. This is an inherent limitation of Arrow's nanosecond timestamp representation.
 
 :::
 

website/versioned_docs/version-1.10.x/components/data-connectors/oracle.md

@@ -117,7 +117,6 @@ The table below shows the Oracle data types supported, along with the type mappi
 :::note
 
 - The Oracle `TIMESTAMP WITH LOCAL TIME ZONE` value is retrieved as a UTC time value.
-- `TIMESTAMP`, `TIMESTAMP WITH TIME ZONE`, and `TIMESTAMP WITH LOCAL TIME ZONE` columns with non-zero precision are mapped to `Timestamp(Nanosecond)`. Timestamps outside the nanosecond range (approximately years 1677–2262) will silently return `1970-01-01 UTC`. This is an inherent limitation of Arrow's nanosecond timestamp representation.
 
 :::
 

website/versioned_docs/version-1.11.x/components/data-accelerators/postgres/index.md

@@ -34,8 +34,8 @@ The connection to PostgreSQL can be configured by providing the following `param
   - `prefer`: This mode will try to establish a secure TLS connection if possible, but will connect insecurely if the server does not support TLS.
   - `disable`: This mode will not attempt to use a TLS connection, even if the server supports it.
 - `pg_sslrootcert`: Optional parameter specifying the path to a custom PEM certificate that the connector will trust.
-- `pg_connection_pool_min_idle`: Optional. The minimum number of idle connections to keep open in the pool. Default is `1`.
-- `connection_pool_size`: Optional. The maximum number of connections to keep open in the connection pool. Default is `5`.
+- `pg_connection_pool_min`: Optional. The minimum number of connections to keep open in the pool, lazily created when requested. Default is `5`.
+- `connection_pool_size`: Optional. The maximum number of connections created in the connection pool. Default is `10`.
 
 Configuration `params` are provided in the `acceleration` section of a dataset.
 

website/versioned_docs/version-1.11.x/components/data-connectors/mssql.md

@@ -12,7 +12,6 @@ The Microsoft SQL Server Data Connector enables federated/accelerated SQL querie
 
 1. The connector supports SQL Server authentication (SQL Login and Password) only.
 1. Spatial types (`geography`) are not supported, and columns with these types will be ignored.
-1. `DATETIME2` and `DATETIMEOFFSET` columns are mapped to Arrow `Timestamp(Nanosecond)`. Timestamps outside the nanosecond range (approximately years 1677–2262) will silently return `1970-01-01 UTC`. This is an inherent limitation of Arrow's nanosecond timestamp representation.
 
 :::
 

website/versioned_docs/version-1.11.x/components/data-connectors/oracle.md

@@ -117,7 +117,6 @@ The table below shows the Oracle data types supported, along with the type mappi
 :::note
 
 - The Oracle `TIMESTAMP WITH LOCAL TIME ZONE` value is retrieved as a UTC time value.
-- `TIMESTAMP`, `TIMESTAMP WITH TIME ZONE`, and `TIMESTAMP WITH LOCAL TIME ZONE` columns with non-zero precision are mapped to `Timestamp(Nanosecond)`. Timestamps outside the nanosecond range (approximately years 1677–2262) will silently return `1970-01-01 UTC`. This is an inherent limitation of Arrow's nanosecond timestamp representation.
 
 :::
 

website/versioned_docs/version-1.5.x/components/data-connectors/mssql.md

@@ -12,7 +12,6 @@ The Microsoft SQL Server Data Connector enables federated/accelerated SQL querie
 
 1. The connector supports SQL Server authentication (SQL Login and Password) only.
 1. Spatial types (`geography`) are not supported, and columns with these types will be ignored.
-1. `DATETIME2` and `DATETIMEOFFSET` columns are mapped to Arrow `Timestamp(Nanosecond)`. Timestamps outside the nanosecond range (approximately years 1677–2262) will silently return `1970-01-01 UTC`. This is an inherent limitation of Arrow's nanosecond timestamp representation.
 
 :::
 

website/versioned_docs/version-1.5.x/components/data-connectors/oracle.md

@@ -117,7 +117,6 @@ The table below shows the Oracle data types supported, along with the type mappi
 :::note
 
 - The Oracle `TIMESTAMP WITH LOCAL TIME ZONE` value is retrieved as a UTC time value.
-- `TIMESTAMP`, `TIMESTAMP WITH TIME ZONE`, and `TIMESTAMP WITH LOCAL TIME ZONE` columns with non-zero precision are mapped to `Timestamp(Nanosecond)`. Timestamps outside the nanosecond range (approximately years 1677–2262) will silently return `1970-01-01 UTC`. This is an inherent limitation of Arrow's nanosecond timestamp representation.
 
 :::
 

website/versioned_docs/version-1.6.x/components/data-connectors/mssql.md

@@ -12,7 +12,6 @@ The Microsoft SQL Server Data Connector enables federated/accelerated SQL querie
 
 1. The connector supports SQL Server authentication (SQL Login and Password) only.
 1. Spatial types (`geography`) are not supported, and columns with these types will be ignored.
-1. `DATETIME2` and `DATETIMEOFFSET` columns are mapped to Arrow `Timestamp(Nanosecond)`. Timestamps outside the nanosecond range (approximately years 1677–2262) will silently return `1970-01-01 UTC`. This is an inherent limitation of Arrow's nanosecond timestamp representation.
 
 :::