Results of 1 - 10 of about 53 for enabled (0.002 sec.)
- Building Extensions 13023
- Extensions can be built from source and installed from the resulting local binary. Building Extensions To build using extension flags, set the BUILD_EXTENSIONS flag to the list of extensions that you want to be built. For example: BUILD_EXT
...nked into DuckDB. Unlike TPC-H and TPC-DS, jemalloc is not an extension. It is only supported on 64-bit Linux, where it is enabled by default. To disable it, set BUILD_JEMALLOC=0 . BUILD_TPCE When this flag is set, the TPCE library is built. Unlike TPC-...H and TPC-DS this is not a proper extension and it's not distributed as such. Enabling this allows TPC-E enabled queries through our test suite. Debug Flags CRASH_ON_ASSERT D_ASSERT(condition) is used all throughout the code, these wil...l throw an InternalException in debug builds. With this flag enabled, when the assertion triggers it will instead directly cause a crash. DISABLE_STRING_INLINE In our execution format string_... - https://man.mtool.work/duckdb/2.0/dev/building/building_extensions.html
- Profile and Monitor 12339
- Overview The Rust client can observe a running or completed query: it can retrieve per-operator profiling metrics after a query runs, and interrupt a long-running query from another thread. Both are shown below. Profiling Profiling must be
...Connection::open_in_memory()?; // Do not print profiling output to stdout after each query (the default when profiling is enabled). conn.execute("PRAGMA enable_profiling = 'no_output'", [])?; conn.execute("SELECT 42", [])?; let info = conn.get_profilin...g_info().expect("profiling should be enabled"); println!("profiled children: {}", info.children.len()); get_profiling_info() returns an Option<ProfilingInfo> , which i...s None when profiling is not enabled. ProfilingInfo is a tree whose metrics are grouped and named in lowercase (see the metrics list ): the root's children are... - https://man.mtool.work/duckdb/2.0/clients/rust/profiling.html
- Configuration 9764
- DuckDB has a number of configuration options that can be used to change the behavior of the system. The configuration options can be set using either the SET statement or the PRAGMA statement . They can be reset to their original values usi
..."did you mean..." error message. UBIGINT 100 checkpoint_on_detach Override checkpoint behavior when detaching a database. ENABLED requests a checkpoint, but the checkpoint does not occur if another connection still references the database. DISABLED nev...keep bulk appends in memory, e.g., for in-memory benchmarks. BOOLEAN true enable_optimizer Whether the query optimizer is enabled. BOOLEAN true enable_server_cert_verification Enable server side certificate verification. BOOLEAN false enable_view_depen...dencies Enable created VIEWs to create dependencies on the referenced objects, such as tables. BOOLEAN false enabled_log_types Sets the list of enabled log types. VARCHAR error_on_division_by_zero Throw an error instead of returning NULL w... - https://man.mtool.work/duckdb/2.0/configuration/overview.html
- Profile and Monitor 9585
- Overview The JDBC driver exposes several ways to observe a running or completed query: cancelling and timing out queries, polling query progress, retrieving profiling output, and emitting memory-usage events through Java Flight Recorder . T
...ther JFR is recording or the sampling period; those are governed by the JFR recording settings. Controlling the Period and Enabled State The sampling rate and enabled state are JFR-native settings. Configure them in a .jfc profile, through JMC, or progr...... r.stop(); r.dump(Path.of("app.jfr")); } The equivalent .jfc snippet: <event name="duckdb.MemoryUsage"> <setting name="enabled">true</setting> <setting name="period">1 s</setting> </event> When no recording enables the event, the driver does no work...: the underlying duckdb_memory() query is never issued. Event Schema While a recording is active with the event enabled, the driver emits one duckdb.MemoryUsage event per DuckDB memory tag per JFR tick, with the following fields: Field Type D... - https://man.mtool.work/duckdb/2.0/clients/java/profiling.html
- Iceberg Options 9585
- This page lists the options of the iceberg extension: the parameters accepted by the Iceberg functions , the options of the ATTACH and CREATE SECRET statements used to connect to a catalog , and the global settings. ATTACH Options To make a
...aders (key-value) sent along with the requests to the REST Catalog. DEFAULT_TABLE_LOCATION_FROM_NAMESPACE BOOLEAN false If enabled, a CREATE TABLE without an explicit WITH ('location' = …) clause derives the table location as ⟨namespace location⟩/⟨table...ed before use and cannot be empty. Defaults to the ASCII unit separator ( 0x1F ). USE_METADATA_LOCATION BOOLEAN false When enabled, DuckDB loads table metadata from the file at the metadata-location returned by the catalog and treats it as authoritative...ed path. iceberg_metadata_log_clock_skew_ms BIGINT 0 Clock-skew allowance in milliseconds when iceberg_use_metadata_log is enabled. Table metadata written up to this long after the transaction start is considered visible. Set to 0 for strict timestamp c... - https://man.mtool.work/duckdb/2.0/core_extensions/iceberg/iceberg_options.html
- Building Configuration 9421
- Build Types DuckDB can be built in many different settings, most of these correspond directly to CMake but not all of them. release This build has been stripped of all the assertions and debug symbols and code, optimized for performance. de
...c at building DuckDB extensions . Package Flags The Makefile has flags to control which components are built. These can be enabled by either setting them in the current env , through set up files like bashrc or zshrc , or by setting them before the call...se errors can be detected. DISABLE_SANITIZER In some situations, running an executable that has been built with sanitizers enabled is not supported / can cause problems. Julia is an example of this. With this flag enabled, the sanitizers are disabled fo... - https://man.mtool.work/duckdb/2.0/dev/building/build_configuration.html
- PostgreSQL Extension Functions 9243
- 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
...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_millis ( UBIGINT ):...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_thread ( BOOLEAN ):...ds are unable to obtain a connection - they return without doing any work and without throwing an error thread_local_cache_enabled ( BOOLEAN ): whether caching the connections caching in thread-local cache is enabled; thread-local connections are NOT cl... - https://man.mtool.work/duckdb/2.0/core_extensions/postgres/functions.html
- Troubleshoot 9079
- Overview This page collects common issues encountered when using the DuckDB Go client, together with their workarounds. Because the client uses cgo to embed DuckDB, most build problems are cgo or linker problems. If you run into a problem t
...off automatically when cross-compiling. Re-enable it and point at the right cross-compiler: bash CC=⟨c_cross_compiler⟩ CGO_ENABLED=1 go build Windows Setup On Windows you need a compatible version of gcc and the necessary runtime libraries. One way is M..., .dylib on macOS) from the DuckDB releases page , then build and run with the library on the loader path: # On Linux. CGO_ENABLED=1 CGO_LDFLAGS="-lduckdb -L/path/to/libs" go build -tags=duckdb_use_lib main.go LD_LIBRARY_PATH=/path/to/libs ./main # On m...acOS. CGO_ENABLED=1 CGO_LDFLAGS="-lduckdb -L/path/to/libs" go build -tags=duckdb_use_lib main.go DYLD_LIBRARY_PATH=/path/to/libs ./main TIME... - https://man.mtool.work/duckdb/2.0/clients/go/troubleshoot.html
- PostgreSQL Extension Connection Pool 8900
- 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
...that exceed idle_timeout_millis or max_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_milli...is checked when the connection is taken from the pool and returned to the pool. When the connection pool reaper thread is enabled ( pg_pool_enable_reaper_thread option), then this number is checked in background periodically. pg_pool_idle_timeout_milli...in the pool. This number is checked when the connection is taken from the pool. When the connection pool reaper thread is enabled ( pg_pool_enable_reaper_thread option), then this number is checked in background periodically. pg_pool_enable_reaper_thre... - https://man.mtool.work/duckdb/2.0/core_extensions/postgres/connection_pool.html
- PostgreSQL Extension 8722
- The postgres extension allows DuckDB to directly read and write data from a running PostgreSQL database instance. The data can be queried directly from the underlying PostgreSQL database. Data can be loaded from PostgreSQL tables into DuckD
...ool_* ) are documented on the Connection Pool page and the schema cache settings ( pg_staleness_query , pg_staleness_query_enabled ) in the Schema Cache section. Schema Cache To avoid having to continuously fetch schema data from PostgreSQL, DuckDB keep...s added using a "staleness query" (contributed by Brandon Freeman in duckdb/duckdb-postgres#514 ): when pg_staleness_query_enabled option ( BOOLEAN , default: enabled for PostgreSQL, disabled when pg_use_information_schema_introspection is set) is enabl... - https://man.mtool.work/duckdb/2.0/core_extensions/postgres/overview.html
DuckDB 2.0 Documentation / man.mtool.work