Pool: support configuring acquire mode#444
Merged
staticlibs merged 1 commit intoduckdb:mainfrom Apr 18, 2026
Merged
Conversation
This PR adds new configuration option: - `pg_pool_acquire_mode` (`VARCHAR`, default: 'force'): how to acquire connections from the pool: 'force' (always connect, ignore pool limit), 'wait' (block until available), 'try' (fail immediately if unavailable) This option is only applied to Postgres databases attached after the option is set. To configure it for Postgres database that is already attached, the `acquire_mode` named parameter is also added to `postgres_configure_pool()` function: ```sql FROM postgres_configure_pool(catalog_name='s', acquire_mode='wait') ``` Note, before this option the default pool behaviour was `wait`, now the default behaviour is changed to `force`.
2 tasks
staticlibs
added a commit
to staticlibs/duckdb-postgres
that referenced
this pull request
Apr 20, 2026
This PR changes the default scope from `SESSION` to `GLOBAL` for the following options (see duckdb#430 and duckdb#444 for details): - `pg_pool_acquire_mode` - `pg_pool_max_connections` - `pg_pool_wait_timeout_millis` - `pg_pool_enable_thread_local_cache` - `pg_pool_max_lifetime_millis` - `pg_pool_idle_timeout_millis` - `pg_pool_enable_reaper_thread` - `pg_pool_health_check_query` Additionally it changes the default size of the connection pool to `max(cpu_count * 1.5, 8)`. Fixes: duckdb/ducklake#1031
staticlibs
added a commit
that referenced
this pull request
Apr 20, 2026
This PR changes the default scope from `SESSION` to `GLOBAL` for the following options (see #430 and #444 for details): - `pg_pool_acquire_mode` - `pg_pool_max_connections` - `pg_pool_wait_timeout_millis` - `pg_pool_enable_thread_local_cache` - `pg_pool_max_lifetime_millis` - `pg_pool_idle_timeout_millis` - `pg_pool_enable_reaper_thread` - `pg_pool_health_check_query` Additionally it changes the default size of the connection pool to `max(cpu_count * 1.5, 8)`. Fixes: duckdb/ducklake#1031
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds new configuration option:
pg_pool_acquire_mode(VARCHAR, default: 'force'): how to acquire connections from the pool: 'force' (always connect, ignore pool limit), 'wait' (block until available), 'try' (fail immediately if unavailable)This option is only applied to Postgres databases attached after the option is set.
To configure it for a Postgres database that is already attached, the
acquire_modenamed parameter is also added topostgres_configure_pool()function:Note, before this option the default pool behaviour was
wait, now the default behaviour is changed toforce.