AWS redshift documentation change
Summary
Added SQL example to check transaction commit status via sys_transaction_history join
Security assessment
Enhances operational documentation for query/transaction tracking. No direct security implications.
Diff
diff --git a/redshift/latest/dg/SYS_QUERY_HISTORY.md b/redshift/latest/dg/SYS_QUERY_HISTORY.md index f29183e22..55372243d 100644 --- a//redshift/latest/dg/SYS_QUERY_HISTORY.md +++ b//redshift/latest/dg/SYS_QUERY_HISTORY.md @@ -12,0 +13,17 @@ SYS_QUERY_HISTORY is visible to all users. Superusers can see all rows; regular +###### Note + +To verify whether a transaction containing the executed query was successfully committed, you need to perform a join operation between system tables and the `sys_transaction_history` table. For example: + + + SELECT + qh.transaction_id, + qh.query_id, + qh.status AS query_status, + qh.query_type, + TRIM(qh.query_text) AS query_text, + th.status AS transaction_status + FROM + sys_query_history qh + LEFT JOIN + sys_transaction_history th ON qh.transaction_id = th.transaction_id; +