Show help message.
Analyze your query (
WITH) and generate recommendations.
EXPLAIN is applied, immediately providing the plan without execution, to understand the plan structure and the planner costs and estimated row numbers for each node in the plan. Right after that,
EXPLAIN (ANALYZE, BUFFERS) for the same query will be used to get the execution plan with all the details: the actual time of execution for each node in the plan, the actual number of rows, numbers of shared buffers hit and read, and so on. Please read the chapter "Using
EXPLAIN" in the official PostgreSQL documentation.
The final result is provided in both JSON and textual forms. The data is never provided, only meta-data (the detailed plans, timing).
Analyze the specified query (
WITH) without execution.
EXPLAIN is applied, immediately providing the plan without execution, to understand the plan structure and the planner costs and estimated row numbers for each node in the plan.
If the plan uses a HypoPG index, an additional
EXPLAIN for the same query will be executed to obtain the plan without execution, with the HypoPG extension turned off.
The final result is provided with all available plans without execution. The data is never provided, users get only meta-data.
Execute any query (for example,
The data output is never provided, users see only the time spent on the execution or errors, if any.
Show currently running sessions in Postgres (states:
idle in transaction,
Terminate Postgres backend that has the specified PID.
Revert the database to the initial state. Usually takes less than a minute.
All database changes applied during the session are discarded and cannot be restored.
psql meta-commands are supported:
\d+– relations (tables, views, materialized views, indexes),
\dm+– materialized views,
See the official PostgreSQL documentation for details.
Create hypothetical indexes using the HypoPG extension. This allows verifying index ideas without actually building large indexes.
⚠ Note that an extended Postgres image for Database Lab is required. For a quick start, you can use prepared images created by Postgres.ai, or prepare your own.
The following subcommands are supported:
hypo [CREATE_INDEX_QUERY]– create a hypothetical index. For example,
hypo create index hypo_index_test on table1 using btree (id).
hypo desc– describe all hypothetical indexes.
hypo desc [OID]– describe the specified hypothetical index. For example,
hypo desc 18284.
hypo drop [OID]– drop the specified hypothetical index. For example,
hypo drop 18284.
hypo reset– drop all hypothetical indexes.