AWS Security ChangesHomeSearch

AWS redshift documentation change

Service: redshift · 2025-05-10 · Documentation low

File: redshift/latest/dg/SYS_QUERY_DETAIL.md

Summary

Added SQL example to verify transaction commit status via sys_transaction_history join

Security assessment

Improves documentation for transaction verification but does not address security vulnerabilities or describe security features.

Diff

diff --git a/redshift/latest/dg/SYS_QUERY_DETAIL.md b/redshift/latest/dg/SYS_QUERY_DETAIL.md
index 561f2afa3..ea38c824f 100644
--- a//redshift/latest/dg/SYS_QUERY_DETAIL.md
+++ b//redshift/latest/dg/SYS_QUERY_DETAIL.md
@@ -12,0 +13,14 @@ SYS_QUERY_DETAIL is visible to all users. Superusers can see all rows; regular u
+###### 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 
+        th.transaction_id,
+        qd.query_id,
+        th.status AS transaction_status
+    FROM 
+        sys_query_detail qd
+    LEFT JOIN sys_query_history qh ON qd.query_id = qh.query_id
+    LEFT JOIN sys_transaction_history th on qh.transaction_id = th.transaction_id;
+