You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
148007: sql,log: add new txn_timestamp filed to CommonSqlEventDetails r=kyle-a-wong a=kyle-a-wong
Previously, an event's `timestamp` field was either set to the current time, or the read timestamp of the txn emitting the event, if the event was emitted within a txn. This isn't obvious functionality and can result in events to be seemingly out of order.
To fix this, we adeded a new `txn_timestamp` field to the CommonSQLEventDetails proto type. This field is responsible for holding the txn's current read timestamp that a structured event was emitted in, if in a transaction. Now, an event's timestamp will always be the time that the event was constructred, and txn_timestamp will transactions current read timestamp.
Resolves: #146820
Epic: None
Release note (general change): Updated SQL events to have a 'TxnTimestamp' which indicates the read timestamp of the transaction that the sql event was emitted in, if in a transaction. The `Timestamp` of an event will always be the time that the event was created.
148247: explain: shorten some extremely long lines r=yuzefovich a=yuzefovich
I just saw a bundle with an ANY clause with a tuple that had 10k
elements. As of 4c77e2a, we shortened
the tuple itself to not pollute `plan.txt` too much, but the type
declaration still had the word "string" printed 10k times. This is the
case when explicit `TYPES` format of EXPLAIN is requested, or when the
bundle collected via EXPLAIN ANALYZE (DEBUG) (in which case we always
request the `TYPES` flag).
This commit applies the same shortening logic to the type string as we
did in the change mentioned above - if `FmtShortenConstants` flag is
set, then only the first two and the last tuple elements are printed,
reducing the redundant information (chances are all elements within the
tuple are of the same type anyway).
When `VERBOSE` option is set, we show physical spans via `SpanFormatFn`.
This function could be called for Scan, Vector Search, and Delete Range
operators. Unlike in non-verbose case (where we only print the first
4 logical spans), previously we would print any number of physical plans
in the verbose mode. In the same bundle we had 10k of spans which
significantly polluted `plan.txt`, so this commit introduces a hard
limit - now the first 20 physical spans will be printed.
Informs: https://cockroachdb.zendesk.com/agent/tickets/27348
Epic: None
Release note: None
Co-authored-by: Kyle Wong <[email protected]>
Co-authored-by: Yahor Yuzefovich <[email protected]>
0 commit comments