⌘K ctrl+k
Search Shortcut cmd + k | ctrl + k
DuckDB 2.0 ドキュメント 全文検索
per page, with , order by , clip by
Results of 1 - 6 of about 6 for reaper (0.001 sec.)
PostgreSQL Extension Connection Pool 11790
PostgreSQL server spawns a backend process for every incoming client connection. This model leads to the two following points with the postgres extension that can cause performance problems: opening a new connection is relatively expensive ... ption or postgres_configure_pool function) or to disable the pooling completely (by setting pg_pool_max_connections = 0 ). Reaper Thread The postgres extension supports running a background thread (so called "reaper thread") that periodically scans idl ... _lifetime_millis values. Separate thread is run for each connections pool, it can be enabled/disabled using pg_pool_enable_reaper_thread configuraton option. When the reaper thread is not running, idle_timeout_millis or max_lifetime_millis values of th ... ad of the main cache shared between all threads. Warning Thread-local connection are not checked and not cleaned up by the reaper thread. Thread-local cache should be used with caution as cached connections, while not available to other threads, are st ...
https://man.mtool.work/duckdb/2.0/core_extensions/postgres/connection_pool.html
PostgreSQL Extension Functions 10931
postgres_clear_cache postgres_configure_pool postgres_execute postgres_hstore_get postgres_hstore_to_json postgres_query read_postgres_binary postgres_clear_cache postgres_clear_cache() -> TABLE Clears cached schema entries (like table name ... open. This number is checked when the connection is taken from the pool and returned to the pool. When the connection pool reaper thread is enabled ( enable_reaper_thread argument), then this number is checked in background periodically. idle_timeout_m ... can be kept idle in the pool. This number is checked when the connection is taken from the pool. When the connection pool reaper thread is enabled ( enable_reaper_thread option), then this number is checked in background periodically. enable_reaper_th ... read ( BOOLEAN ): whether to enable the connection pool reaper thread, that periodically scans the pool to check the max_lifetime_millis and idle_timeout_millis and closes the connectio ...
https://man.mtool.work/duckdb/2.0/core_extensions/postgres/functions.html
Out of Memory Errors 9870
DuckDB has a state of the art out-of-core query engine that can spill to disk for larger-than-memory processing. We continuously strive to improve DuckDB's scalability and prevent out of memory errors whenever possible. That said, you may s ... e memory allocator. For example: Out of Memory Error: failed to pin block of size 256.0 KiB (476.7 MiB/476.8 MiB used) OOM Reaper (Linux) Many Linux distributions have an OOM killer or OOM reaper process whose goal is to prevent memory overcommitment. ... If the OOM reaper killed your process, you often see the following message where DuckDB was running: Killed To get more detailed information ... e diagnostic messages using the dmesg command (you may need sudo ): sudo dmesg If the process was killed by the OOM killer/reaper, you will find an entry like this: [Fri Apr 18 02:04:10 2025] Out of memory: Killed process 54400 (duckdb) total-vm:103791 ...
https://man.mtool.work/duckdb/2.0/guides/troubleshooting/oom_errors.html
Out-of-Memory Issues 7622
Configuration Options If you are experiencing out-of-memory issues with DuckDB, try tweaking the following configuration options: Reduce the number of threads using the SET threads = ... command. Setting the memory limit lower than the defa ... ve more memory than allowed by the memory limit. If this happens (e.g., DuckDB is killed by the operating system or an OOM reaper process), set the memory limit to just 50-60% of the total system memory by using the SET memory_limit = '...' statement. ...
https://man.mtool.work/duckdb/2.0/guides/performance/oom.html
Crashes 7348
DuckDB is thoroughly tested via an extensive test suite. However, bugs can still occur and these can sometimes lead to crashes. This page contains practical information on how to troubleshoot DuckDB crashes. Types of Crashes There are a few ... crash can also be a symptom of the operating system killing the process. For example, many Linux distributions run an OOM reaper or OOM killer process , which kills processes to free up their memory and thus prevents the operating system from running ...
https://man.mtool.work/duckdb/2.0/guides/troubleshooting/crashes.html
MySQL Extension 7220
The mysql extension allows DuckDB to directly read and write data from/to a running MySQL instance. The data can be queried directly from the underlying MySQL database. Data can be loaded from MySQL tables into DuckDB tables, or vice versa. ... pened; when exceeded, the connection is closed instead of being returned to the cache ( 0 disables it) 0 mysql_pool_enable_reaper_thread Whether to run a dedicated thread that periodically scans the pool and removes expired connections true mysql_pool_ ...
https://man.mtool.work/duckdb/2.0/core_extensions/mysql.html
PREV 1 NEXT
DuckDB 2.0 Documentation / man.mtool.work