PR #93644 - sql: enhance SHOW RANGES (6 of 6)

[cockroach-teamcity]

Exalate commented:

Related PR: cockroachdb/cockroach#93644
Commit: cockroachdb/cockroach@e67d2fd

---

Release note (sql change): The following new statements are
introduced:

• SHOW RANGES FROM CURRENT_CATALOG and SHOW RANGES without
  parameter: alias for SHOW RANGES FROM DATABASE on the session's
  current database.

• SHOW RANGES FROM DATABASE ... WITH TABLES
  Reports at least one row per table. It's possible for the same
  range ID to be repeated across multiple rows, when a range spans
  multiple tables.

• SHOW RANGES FROM DATABASE ... WITH INDEXES
  Reports at least one row per index. It's possible for the same
  range ID to be repeated across multiple rows, when a range spans
  multiple indexes.

• SHOW RANGES FROM TABLE ... WITH INDEXES
  Reports at least one row per index. It's possible for the same
  range ID to be repeated across multiple rows, when a range spans
  multiple indexes.

• SHOW CLUSTER RANGES [ WITH { INDEXES ]( TABLES } ) Reports ranges
  across the entire cluster, including ranges that don't contain table
  data. The behavior of WITH INDEXES and WITH TABLES is the same
  as for SHOW RANGES FROM DATABASE.

Additionally, the following new options have been added to the SHOW RANGES statement:

• WITH KEYS: produce the raw bytes of the start/end key boundaries.
• WITH DETAILS: produce more details, using computations that
  require extra network roundtrips. Makes the operation slower
  overall.
• WITH EXPLAIN: produce the text of the SQL query used to
  run the statement.

Jira Issue: DOC-6472

[knz]

NB: The new behavior will be opt-in in v23.1, and the old behavior becomes deprecated.
See: cockroachdb/cockroach#98979