Search Result: GetProfilingInfo - DuckDB 2.0 全文検索

Profile and Monitor 9414: 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 ... rofiling on that connection with the enable_profiling setting , run the query to profile, then read the result with duckdb.GetProfilingInfo() : db, err := sql.Open("duckdb", "") check(err) defer db.Close() conn, err := db.Conn(context.Background()) check(err) de ... xt.Background(), `SELECT 42`) check(err) res.Close() // Retrieve the metrics collected for that query. info, err := duckdb.GetProfilingInfo(conn) check(err) // Optionally, turn profiling off again. _, err = conn.ExecContext(context.Background(), `PRAGMA disable_ ... profiling`) check(err) GetProfilingInfo() returns a duckdb.ProfilingInfo , a tree that mirrors DuckDB's query plan. Each node has a Metrics map of metric name to ...; https://man.mtool.work/duckdb/2.0/clients/go/profiling.html

PREV 1 NEXT

DuckDB 2.0 Documentation / man.mtool.work