From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Cc: | ewtoombs(at)uwaterloo(dot)ca |
Subject: | BUG #16065: The operation nodes in query plans outputted by EXPLAIN have no authoritative definitions. |
Date: | 2019-10-18 15:01:55 |
Message-ID: | 16065-4c4eddc338dbd871@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 16065
Logged by: Eric Toombs
Email address: ewtoombs(at)uwaterloo(dot)ca
PostgreSQL version: 12.0
Operating system: any
Description:
The official documentation of EXPLAIN is here:
https://www.postgresql.org/docs/current/sql-explain.html
It's a start, but it doesn't actually define any of the operation nodes in
the query plan tree it outputs, e.g. Seq Scan, Index Scan, Index Only Scan,
HashAggregate, Nested Loop, Nested Loop Semi Join, Nested Loop Anti Join,
etc.. Online, there are descriptions (i.e. guesses) of what each operation
node is actually doing, but these descriptions are not authoritative.
With authoritative definitions of each operation node, there would be no
more guesswork, and DBAs could have a much more reliable mental model of
what a query plan actually does.
From | Date | Subject | |
---|---|---|---|
Next Message | PG Bug reporting form | 2019-10-18 19:47:56 | BUG #16066: Ldap Authentication failure on PostgreSQL 10.10 |
Previous Message | Alvaro Herrera | 2019-10-18 11:40:17 | Re: BUG #16026: default_tablespace in postgresql.conf is used instead of the database's default. |