supabase/supabase · apps/docs/content/guides/database/inspect.mdx
When you include `analyze` in the explain statement, the database attempts to execute the query and provides a detailed query plan along with actual execution times. So, be careful using `explain analyze` with `insert`/`update`/`delete` queries, because the query will actually ru…
https://www.postgresql.org/docs/current/sql-explain.html
Also note that the numbers, and even the selected query strategy, might vary between PostgreSQL releases due to planner improvements. In addition, the ANALYZE command uses random sampling to estimate data statistics; therefore, it is possible for cost estimates to change after a …
https://www.postgresql.org/docs/current/sql-explain.html
EXPLAIN — show the execution plan of a statement EXPLAIN [ (option [, ...] ) ]statement whereoption can be one of: ANALYZE [boolean ] VERBOSE [boolean ] COSTS [boolean ] SETTINGS [boolean ] GENERIC_PLAN [boolean ] BUFFERS [boolean ] SERIALIZE [ { NONE | TEXT | BINARY } ] WAL [boo…
supabase/supabase · apps/docs/content/guides/database/debugging-performance.mdx
--- id: 'debugging-performance' title: 'Debugging performance issues' description: 'Debug slow-running queries using the Postgres execution planner.' subtitle: 'Debug slow-running queries using the Postgres execution planner.' --- `explain()` is a method that provides the Postgr…
apache/flink · docs/content/docs/sql/reference/utility/explain.md
--- title: "EXPLAIN Statements" weight: 9 type: docs aliases: - /docs/sql/reference/explain/ - /dev/table/sql/explain.html --- <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this wo…
supabase/supabase · apps/docs/content/guides/database/query-optimization.mdx
--- title: 'Query Optimization' description: 'Choosing indexes to improve your query performance.' subtitle: 'Choosing indexes to improve your query performance.' footerHelpType: 'postgres' --- When working with Postgres, or any relational database, indexing is key to improving …
https://www.postgresql.org/docs/current/auto-explain.html
The auto_explain module provides a means for logging execution plans of slow statements automatically, without having to run EXPLAIN by hand. This is especially helpful for tracking down un-optimized queries in large applications. The module provides no SQL-accessible functions. …
supabase/supabase · apps/docs/content/guides/database/inspect.mdx
--- title: 'Debugging and monitoring' description: 'Inspecting your Postgres database for common issues around disk, query performance, index, locks, and more using the terminal.' --- Database performance is a large topic and many factors can contribute. Some of the most common …
https://docs.pingcap.com/tidb/dev/explain-walkthrough/
Because SQL is a declarative language, you cannot automatically tell whether a query is executed efficiently. You must first use the EXPLAIN statement to learn the current execution plan. The following statement from the bikeshare example database counts how many trips were taken…
https://docs.pingcap.com/tidb/dev/explain-walkthrough/
In the following output, you can see that a new execution plan is chosen, and the TableFullScan and Selection operators have been eliminated: EXPLAIN SELECT count(*) FROM trips WHERE start_date BETWEEN '2017-07-01 00:00:00' AND '2017-07-01 23:59:59'; +----------------------------…