Results of 1 - 10 of about 98 for Running (0.001 sec.)
- Profile and Monitor 11421
- 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
...total_time . Read a node's metrics through its metrics map and its children through children . Interrupting Queries A long-running query can be cancelled from another thread. Call interrupt_handle() on the connection to get an Arc<InterruptHandle> . Int...t = join_handle.join().unwrap(); assert!(query_result.is_err()); Ok(()) } interrupt() cancels whichever query is currently running on the connection the handle was obtained from. If the connection has already been dropped, calling interrupt() is a no-op...Profiling — DuckDB's query profiling output and the enable_profiling PRAGMA and the tracked_metrics setting. Run Queries — running the queries whose metrics this page reads and whose execution it interrupts. Connect — the Connection that profiling and t... - https://man.mtool.work/duckdb/2.0/clients/rust/profiling.html
- DuckDB Environment 10885
- DuckDB provides a number of functions and PRAGMA options to retrieve information on the running DuckDB instance and its environment. Version The version() function returns the version number of DuckDB. SELECT version() AS version; version v
...tform is used when installing extensions . To retrieve the platform, use the following PRAGMA : PRAGMA platform; On macOS, running on Apple Silicon architecture, the result is: platform osx_arm64 On Windows, running on an AMD64 architecture, the platfor...m is windows_amd64 . On Ubuntu Linux, running on the ARM64 architecture, the platform is linux_arm64 . Extensions To get a list of DuckDB extensions and their status (e... - https://man.mtool.work/duckdb/2.0/guides/meta/duckdb_environment.html
- Securing Extensions 10885
- DuckDB has a powerful extension mechanism, which has the same privileges as the user running DuckDB's (parent) process. This introduces security considerations. Therefore, we recommend reviewing the configuration options listed on this page
...llow_unsigned_extensions = true at startup (e.g., duckdb -unsigned in the CLI). It cannot be changed while the database is running. Security-related configuration settings lock themselves , i.e., it is only possible to restrict capabilities in the curre...allow_community_extensions = true; Invalid Input Error: Cannot change allow_community_extensions setting while database is running Custom Extension Repositories DuckDB 2.0 introduced trusted custom extension repositories , which can serve extensions sig...ies) or 'undecided' (the default: blocks adding new repositories, but keeps trusting existing ones). While the database is running, the setting can only move from 'undecided' to 'allowed' or 'forbidden' , or from 'allowed' to 'forbidden' . extension_rep... - https://man.mtool.work/duckdb/2.0/operations_manual/securing_duckdb/securing_ext...
- Securing DuckDB 10349
- DuckDB is a powerful analytical database engine. It can read and write files, access the network, load extensions, and use system resources. Like any powerful tool, these capabilities require appropriate configuration when working with sens
...not execute SQL from untrusted sources without proper sandboxing. DuckDB executes SQL with the full privileges of the user running it, much like a shell or scripting interpreter (such as bash or Python). Just as you wouldn't run an untrusted shell scrip...same caution to SQL in DuckDB. If your application must execute SQL from untrusted sources, use additional safeguards when running untrusted code such as: Use duckdb-wasm for sandboxing Run DuckDB in an isolated container (e.g., Docker with restricted c...to do so will result in an error: Invalid Input Error: Cannot change allow_community_extensions setting while database is running This prevents re-enabling settings that were explicitly disabled. Nevertheless, many configuration settings do not disable... - https://man.mtool.work/duckdb/2.0/operations_manual/securing_duckdb/overview.htm...
- Benchmark Suite 9669
- DuckDB has an extensive benchmark suite. When making changes that have potential performance implications, it is important to run these benchmarks to detect potential performance regressions. Getting Started To build the benchmark suite, ru
...IONS='tpch' make Listing Benchmarks To list all available benchmarks, run: build/release/benchmark/benchmark_runner --list Running Benchmarks Running a Single Benchmark To run a single benchmark, issue the following command: build/release/benchmark/benc...s_addition.benchmark --out=timings.out The output will contain the following: 0.182472 0.185027 0.184163 0.185281 0.182948 Running Multiple Benchmarks Using a Regular Expression You can also use a regular expression to specify which benchmarks to run. B...hell, hence this requires proper quoting or escaping). build/release/benchmark/benchmark_runner "benchmark/micro/nulls/.*" Running All Benchmarks Not specifying any argument will run all benchmarks. build/release/benchmark/benchmark_runner Other Options... - https://man.mtool.work/duckdb/2.0/dev/benchmark.html
- Tuning Workloads 9669
- DuckDB aims to perform well out of the box, so most workloads do not require any tuning. When tuning is worthwhile, there is no single configuration or magic number that is optimal for every workload: the right settings depend on what you a
...uring the spill-to-disk directory Larger-than-memory workloads Diagnosing a slow query Inspecting the query plan Profiling Running the same query many times with different parameters Prepared statements Prepared statements Reading files over a slow or u...nreliable network Tuning asynchronous I/O and minimizing IO Querying remote files Running many small queries Reusing a single connection Best practices for using connections The rest of this page covers each of t...erforming as well as expected, it's worth studying their query plans: Use EXPLAIN to print the physical query plan without running the query. Use EXPLAIN ANALYZE to run and profile the query. This will show the CPU time that each step in the query takes... - https://man.mtool.work/duckdb/2.0/guides/performance/how_to_tune_workloads.html
- Command Line Client 8467
- Installation To use the DuckDB CLI client, visit the CLI installation page . The latest stable version of the DuckDB command line client is 2.0.0. Installation The DuckDB CLI (Command Line Interface) is a single, dependency-free executable.
...s a tldr page , which summarizes the most common uses of the CLI client. If you have tldr installed, you can display it by running tldr duckdb . Getting Started Once the CLI executable has been downloaded, decompress it and save it to any directory. Nav...y» D To open or create a persistent database , simply include a path as a command line argument: duckdb my_database.duckdb Running SQL Statements in the CLI Once the CLI has been opened, enter a SQL statement followed by a semicolon, then hit enter and...d. The .read command requires only one argument: the path to the file containing the SQL and/or commands to execute. After running the commands in the file, control will revert back to the terminal. Output from the execution of that file is governed by... - https://man.mtool.work/duckdb/2.0/clients/cli/overview.html
- Debugging 8337
- The purpose of the tests is to figure out when things break. Inevitably changes made to the system will cause one of the tests to fail, and when that happens the test needs to be debugged. First, it is always recommended to run in debug mod
...and line parameter (e.g., build/debug/test/unittest test/sql/projection/test_simple_projection.test ). For more options on running a subset of the tests see the Triggering which tests to run section. After that, a debugger can be attached to the program...an optional mode unskip . Any queries between the two statements will not be executed. Triggering Which Tests to Run When running the unittest program, by default all the fast tests are run. A specific test can be run by adding the name of the test as...in the “projection” directory: build/debug/test/unittest "[projection]" All tests, including the slow tests, can be run by running the tests with an asterisk. To run all tests, including the slow tests: build/debug/test/unittest "*" We can run a subset... - https://man.mtool.work/duckdb/2.0/dev/sqllogictest/debugging.html
- Benchmarks 8337
- For several of the recommendations in our performance guide, we use microbenchmarks to back up our claims. For these benchmarks, we use datasets from the TPC-H benchmark and the LDBC Social Network Benchmark's BI workload . Datasets We use
....parquet file). The TPC datasets used in the benchmark are generated with the DuckDB tpch extension . A Note on Benchmarks Running fair benchmarks is difficult , especially when performing system-to-system comparison. When running benchmarks on DuckDB,... - https://man.mtool.work/duckdb/2.0/guides/performance/benchmarks.html
- Deploying Quack 8337
- This page collects deployment recipes for running a public-facing Quack server. Today there is one recipe (AWS EC2), we will introduce more over time. On AWS EC2 The fastest way to get a public-facing Quack server is the one-click AWS Cloud
...Formation template maintained alongside the extension. It provisions a small EC2 instance running DuckDB, the quack extension behind nginx and Let's Encrypt TLS. As its output, it surfaces the per-instance token and conn...mation console. What the Stack Provisions An AWS::EC2::Instance from a public AMI (per-region map baked into the template) running DuckDB, the quack extension behind nginx and the Let's Encrypt TLS. An AWS::EC2::SecurityGroup opening ports 80 (ACME chal... - https://man.mtool.work/duckdb/2.0/quack/setup/deployment.html
DuckDB 2.0 Documentation / man.mtool.work