[YSQL] Investigate why read time is not printed in docdb requests and make the request print appropriate information

[pao214]

Jira Link: DB-19796

Description

From a sample request log that sends read time

I0506 13:51:00.236526 3285139 pg_session.cc:366] Session id 2: Applying operation on table pg_database: { READ active: 1 read_time: { read: <invalid> local_limit: <invalid> global_limit: <invalid> in_txn_limit: <invalid> serial_no: 0 } request: client: YQL_CLIENT_PGSQL stmt_id: 89207541055744 schema_version: 0 targets { column_id: -8 } targets { column_id: 0 } targets { column_id: 1 } targets { column_id: 2 } targets { column_id: 3 } targets { column_id: 4 } targets { column_id: 5 } targets { column_id: 6 } targets { column_id: 7 } targets { column_id: 8 } targets { column_id: 9 } targets { column_id: 10 } targets { column_id: 11 } targets { column_id: 12 } targets { column_id: 13 } targets { column_id: 14 } targets { column_id: 15 } column_refs { ids: 0 ids: 1 ids: 2 ids: 3 ids: 4 ids: 5 ids: 6 ids: 7 ids: 8 ids: 9 ids: 10 ids: 11 ids: 12 ids: 13 ids: 14 ids: 15 } is_aggregate: 0 limit: 1024 return_paging_state: 1 table_id: "000000010000300080010000000004ee" where_clauses { tscall { opcode: 21 operands { value { string_value: "7B4F5045585052203A6F706E6F203933203A6F7066756E636964203632203A6F70726573756C7474797065203136203A6F707265747365742066616C7365203A6F70636F6C6C69642030203A696E707574636F6C6C696420393530203A6172677320287B564152203A7661726E6F2031203A7661726174746E6F2032203A76617274797065203139203A7661727479706D6F64202D31203A766172636F6C6C696420393530203A7661726C6576656C7375702030203A7661726E6F73796E2031203A7661726174746E6F73796E2032203A6C6F636174696F6E203232307D207B434F4E5354203A636F6E737474797065203139203A636F6E73747479706D6F64202D31203A636F6E7374636F6C6C696420393530203A636F6E73746C656E203634203A636F6E7374627976616C2066616C7365203A636F6E737469736E756C6C2066616C7365203A6C6F636174696F6E20323330203A636F6E737476616C7565203634205B203131362031303120313039203131322031303820393720313136203130312034392030203020302030203020302030203020302030203020302030203020302030203020302030203020302030203020302030203020302030203020302030203020302030203020302030203020302030203020302030203020302030203020302030203020302030203020302030205D7D29203A6C6F636174696F6E203232387D" } } } } col_refs { column_id: 0 attno: 1 } col_refs { column_id: 1 attno: 2 typid: 19 typmod: -1 collid: 0 } col_refs { column_id: 2 attno: 3 } col_refs { column_id: 3 attno: 4 } col_refs { column_id: 4 attno: 5 } col_refs { column_id: 5 attno: 6 } col_refs { column_id: 6 attno: 7 } col_refs { column_id: 7 attno: 8 } col_refs { column_id: 8 attno: 9 } col_refs { column_id: 9 attno: 10 } col_refs { column_id: 10 attno: 11 } col_refs { column_id: 11 attno: 12 } col_refs { column_id: 12 attno: 13 } col_refs { column_id: 13 attno: 14 } col_refs { column_id: 14 attno: 15 } col_refs { column_id: 15 attno: 16 } ysql_db_catalog_version: 1 ysql_db_oid: 13515 metrics_capture: PGSQL_METRICS_CAPTURE_NONE size_limit: 0 expression_serialization_version: 15 }
I0506 13:51:00.236589 3285139 pg_session.cc:395] Session id 2: Flushing collected operations, using session type: kTransactional num ops: 1

Issue Type

kind/bug

Warning: Please confirm that this issue does not contain any sensitive information

• I confirm this issue does not contain any sensitive information.