Results of 1 - 10 of about 17 for messages (0.002 sec.)
- Logging 14242
- DuckDB implements a logging mechanism that provides users with detailed information about events such as query execution, performance metrics and system events. Warning Logs may contain sensitive information, including secrets and credentia
...queries... SELECT * FROM duckdb_logs; In the CLI client , the default log storage is shell_log_storage , which prints log messages to the console but does not support querying. Therefore, the example above passes storage = 'memory' . In other clients, t...upports different logging levels that control the verbosity of the logs: FATAL : Only logs fatal errors ERROR : Logs error messages WARNING : Logs warnings and errors INFO : Logs general information, warnings and errors (default) DEBUG : Logs detailed de...so calling enable_logging() without a level also captures warnings. Setting level = 'warning' excludes lower-severity INFO messages. Note Switching the CLI to a log storage other than shell_log_storage means that warnings are no longer printed to the con... - https://man.mtool.work/duckdb/2.0/operations_manual/logging/overview.html
- Analyzing a Git Repository 11707
- 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
...her in DuckDB. Common Topics Let's start with a simple question: which topic was the most commonly mentioned in the commit messages: CI, CLI, or Python? SELECT message.lower().regexp_extract('\b(ci|cli|python)\b') AS topic, count(*) AS num_commits FROM c...continuous integration dominate the log! We can also do a more exploratory analysis by looking at all words in the commit messages. To do so, we first tokenize the messages: CREATE TABLE words AS SELECT unnest( message .lower() .regexp_replace('\W', ' '..., format ). We also see the account names of some developers ( mytherin , hawkfish ), which are likely there due to commit messages for merging pull requests (e.g., ”Merge pull request #13776 from Mytherin/expressiondepth” ). Finally, we also see some Du... - https://man.mtool.work/duckdb/2.0/guides/snippets/analyze_git_repository.html
- Profile and Monitor 9638
- Overview The Go client can observe query execution: it can retrieve per-operator profiling metrics after a query runs, and register a log storage that receives DuckDB's log messages. Both are described below. Profiling Profiling information
...option. See the Profiling page and the metrics list for the available metric names. Log Storage DuckDB can forward its log messages to a custom storage registered from Go. Register one on a Connector with duckdb.RegisterLogStorage() , giving it a name an... - https://man.mtool.work/duckdb/2.0/clients/go/profiling.html
- Out of Memory Errors 8690
- 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
...ou often see the following message where DuckDB was running: Killed To get more detailed information, check the 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... - https://man.mtool.work/duckdb/2.0/guides/troubleshooting/oom_errors.html
- Configuration 8379
- 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
..._division_by_zero Throw an error instead of returning NULL when dividing by zero. BOOLEAN true errors_as_json Output error messages as structured JSON instead of as a raw string. BOOLEAN false experimental_metadata_reuse EXPERIMENTAL: Re-use row group an...d be logged. The default is NULL, meaning queries are not logged. VARCHAR logging_level Determines which 'severity' of log messages will be logged. VARCHAR INFO ( WARNING in the CLI) logging_mode Determines which types of log messages are logged. VARCHAR... - https://man.mtool.work/duckdb/2.0/configuration/overview.html
- PEG Parser 8224
- New Starting with DuckDB 2.0, the PEG parser is the default parser. In earlier versions it was an experimental, opt-in feature enabled with enable_peg_parser() , which is no longer required or available. DuckDB uses a parser based on PEG (
...er front end derived from PostgreSQL that earlier versions used. The PEG parser enables better suggestions, improved error messages with precise source locations, and allows extensions to extend the grammar. The PEG grammar was first introduced in DuckDB... - https://man.mtool.work/duckdb/2.0/sql/peg_parser.html
- Troubleshoot 8069
- 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
...urns a *duckdb.Error for errors reported by DuckDB. Use errors.As to handle these errors by category without parsing their messages: _, err := db.Exec(query) if err != nil { var duckdbError *duckdb.Error if errors.As(err, &duckdbError) { switch duckdbErr... - https://man.mtool.work/duckdb/2.0/clients/go/troubleshoot.html
- Result Verification 8069
- The standard way of verifying results of queries is using the query statement, followed by the letter I times the number of columns that are expected in the result. After the query, four dashes ( ---- ) are expected followed by the result v
...that you only use a subset of the error message, so that the test does not break unnecessarily if the formatting of error messages is changed. statement error SELECT * FROM non_existent_table; ---- Table with name non_existent_table does not exist! Rege... - https://man.mtool.work/duckdb/2.0/dev/sqllogictest/result_verification.html
- Unit Tester Configuration 7897
- There are three ways of setting options for the unit tester: Command Line Arguments Configuration File Environment Variables Configuration Options List See the Configuration Options List for the full list of available options. Command Line
...nfiguration , struct should have keys name and value --skip-compiled , --no-skip-compiled Skip compiled tests --skip-error-messages <comma-separated strings> Skip rather than fail tests that fail with a message that contains any of these substrings --ski... - https://man.mtool.work/duckdb/2.0/dev/sqllogictest/test_configuration.html
- Reading Faulty CSV Files 7741
- CSV files can come in all shapes and forms, with some presenting many errors that make the process of cleanly reading them inherently difficult. To help users read these files, DuckDB supports detailed error messages, the ability to skip fa
... - https://man.mtool.work/duckdb/2.0/data/csv/reading_faulty_csv_files.html
DuckDB 2.0 Documentation / man.mtool.work