Results of 1 - 10 of about 26 for issue (0.001 sec.)
- Crashes 14977
- 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
...signals: The process stops with a SIGSEGV (segmentation fault), SIGABRT , etc.: these should never occur. Please submit an issue . Internal errors: an operation may result in an Internal Error , e.g.: console INTERNAL Error: Attempted to access index...disk. If you encounter such an error with DuckDB, please run a disk check on the machine and attempt to can reproduce the issue on different computers. If you can reproduce the issue on different setups, report it in the issue tracker . Recovering Da...to use DuckDB with an open pull request applied to the codebase, you can try building it from source . Search for Existing Issues There is a chance that someone else already reported the bug that causes the crash. Please search in the GitHub issue tra... - https://man.mtool.work/duckdb/2.0/guides/troubleshooting/crashes.html
- Internal Errors 11340
- Internal errors signal an assertion failure within DuckDB. They usually occur due to unexpected conditions or errors in the program's logic. For example, running issue 17002 on DuckDB 1.2.1 results in an internal error. INTERNAL Error: Atte
...mpted to access index 3 within vector of size 3 The issue is fixed in DuckDB 1.2.2 and newer versions. After encountering an internal error, DuckDB enters “restricted mode”, where...ever tested. If you encounter an internal error, please consider creating a minimal reproducible example and submitting an issue to the DuckDB issue tracker .... - https://man.mtool.work/duckdb/2.0/dev/internal_errors.html
- Troubleshoot 10794
- Overview This page collects common issues encountered when using DuckDB-Wasm, together with their workarounds. If you run into a problem that is not covered here, search the duckdb-wasm issue tracker on GitHub. Network Error When Querying R
...e Files When DuckDB-Wasm reads a remote file — through the Wasm-flavored httpfs extension or registerFileURL — the browser issues the request, so it is subject to the browser's CORS policy and every request is upgraded to HTTPS. The server hosting the...tten incorrectly (for example to https://http//… ), which breaks reads against local or non-TLS endpoints (see duckdb-wasm issue #2118 ). DuckDB relies on HTTP range requests to read only part of a file. Range requests can fail on Firefox (see issue #...1932 ) and are not detected correctly for some S3 pre-signed URLs (see issue #2228 ), which forces the whole file to be downloaded or makes the read fail. Cached reads of files in DuckDB's native for... - https://man.mtool.work/duckdb/2.0/clients/wasm/troubleshoot.html
- Analyzing a Git Repository 8860
- You can use DuckDB to analyze Git logs using the output of the git log command . Exporting the Git Log We start by picking a character that doesn't occur in any part of the commit log (author names, messages, etc). Since version v1.2.0, Duc
...iovesan?MAIN_BRANCH_VERSIONING: Adopt also for Python build and amalgamation 2025-02-25T12:35:28+01:00?87eff7ebd3?Mark?Fix issue #16377 (#16391) 2025-02-25T10:33:49+01:00?35af26476e?Hannes Mühleisen?Read support for Parquet Float16 Loading the Git Log...MAIN_BRANCH_VERSIONING: Adopt also for Python build and amalgamation │ │ 2025-02-25 12:35:28+01 │ 87eff7ebd3 │ Mark │ Fix issue #16377 (#16391) │ │ 2025-02-25 10:33:49+01 │ 35af26476e │ Hannes Mühleisen │ Read support for Parquet Float16 │ └─────────...│ │ branch │ 6005 │ │ pull │ 5950 │ │ request │ 5945 │ │ add │ 5687 │ │ test │ 3801 │ │ master │ 3289 │ │ tests │ 2339 │ │ issue │ 1971 │ │ main │ 1935 │ │ remove │ 1884 │ │ format │ 1819 │ │ duckdb │ 1710 │ │ use │ 1442 │ │ mytherin │ 1410 │ │ fixes... - https://man.mtool.work/duckdb/2.0/guides/snippets/analyze_git_repository.html
- Swift Client 8232
- DuckDB has a Swift client. See the announcement post for details. Instantiating DuckDB DuckDB supports both in-memory and persistent databases. To work with an in-memory database, run: let database = try Database(store: .inMemory) To work w
...ith a persistent database, run: let database = try Database(store: .file(at: "test.db")) Queries can be issued through a database connection. let connection = try database.connect() DuckDB supports multiple connections per database....ng: "https://exoplanetarchive.ipac.caltech.edu/TAP/sync?query=select+pl_name+,+disc_year+from+pscomppars&format=csv")!) // Issue our first query to DuckDB try connection.execute(""" CREATE TABLE exoplanets AS SELECT * FROM read_csv('\(csvFileURL.path)...re { // Retrieves the number of exoplanets discovered by year func groupedByDiscoveryYear() async throws -> DataFrame { // Issue the query we described above let result = try connection.query(""" SELECT disc_year, count(disc_year) AS Count FROM exopla... - https://man.mtool.work/duckdb/2.0/clients/tertiary_clients/swift.html
- Troubleshoot 8149
- Overview This page collects common issues encountered when using the DuckDB JDBC driver, together with their workarounds. If you run into a problem that is not covered here, search the driver's issue tracker on GitHub. Driver Class Not Foun
...quet directly, for example read_parquet('file.parquet', binary_as_string = true) . This behavior is tracked in duckdb-java issue #113 . Native Image: NoSuchMethodError When Opening a Connection In a GraalVM Native Image executable, opening the first c... - https://man.mtool.work/duckdb/2.0/clients/java/troubleshoot.html
- Legacy Parser Extension 8149
- New The legacy_parser extension was introduced in DuckDB 2.0. DuckDB 2.0.0 replaced the PostgreSQL-derived parser with a new PEG-based parser . The legacy_parser extension allows reverting to the old parser. The PEG parser is designed to be
...that parsed before should continue to parse. If a query that parsed on an earlier version fails on v2.0.0, please file an issue . Installing and Loading To install and load the legacy_parser extension, run: INSTALL AND LOAD legacy_parser; Usage To ac... - https://man.mtool.work/duckdb/2.0/core_extensions/legacy_parser.html
- Known Issues 8083
- Incorrect Memory Values on Old Linux Distributions and WSL 2 On Windows Subsystem for Linux 2 (WSL2), when querying the max_memory or memory_limit from the duckdb_settings , the values may be inaccurate on certain Ubuntu versions (e.g., 20.
...04 and 24.04). The issue also occurs on older distributions such as Red Hat Enterprise Linux 8 (RHEL 8): Example: FROM duckdb_settings() WHERE name... - https://man.mtool.work/duckdb/2.0/clients/cli/known_issues.html
- Benchmark Suite 8083
- 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
...: build/release/benchmark/benchmark_runner --list Running Benchmarks Running a Single Benchmark To run a single benchmark, issue the following command: build/release/benchmark/benchmark_runner benchmark/micro/nulls/no_nulls_addition.benchmark The outp...parameters are expanded in the query, similar to the way that foreach values are expanded in unit tests. Note that we can issue multiple SQL statements in the load section. Once the data is prepared, we are finally ready to specify the query we will... - https://man.mtool.work/duckdb/2.0/dev/benchmark.html
- My Workload Is Slow 7918
- If you find that your workload in DuckDB is slow, we recommend performing the following checks. More detailed instructions are linked for each point. Do you have enough memory? DuckDB works best if you have 1-4 GB memory per thread . Is you
...ager to observe this. Is DuckDB using too many threads? Try limiting the amount of threads . Are you aware of other common issues? If so, please click the Report content issue link below and describe them along with their workarounds.... - https://man.mtool.work/duckdb/2.0/guides/performance/my_workload_is_slow.html
DuckDB 2.0 Documentation / man.mtool.work