Thus far, some statistics tables have been discussed. The idea behind all of them is to see what is going on in the entire system. But what if you are a developer who wants to inspect an individual transaction? pg_stat_xact_user_tables is here to help. It doesn't contain system-wide transactions; it only contains data about your current transaction. This is shown in the following code:

test=# d pg_stat_xact_user_tables 
       View "pg_catalog.pg_stat_xact_user_tables"
    Column     |  Type  | Collation | Nullable | Default 
---------------+--------+-----------+----------+---------
 relid         | oid    |           |          | 
 schemaname    | name   |           |          | 
 relname       | name   |           |          | 
 seq_scan      | bigint |           |          | 
 seq_tup_read  | bigint |           |          | 
 idx_scan      | bigint |           |          | 
 idx_tup_fetch | bigint |           |          | 
 n_tup_ins     | bigint |           |          | 
 n_tup_upd     | bigint |           |          | 
 n_tup_del     | bigint |           |          | 
 n_tup_hot_upd | bigint |           |          | 

Therefore, developers can look into a transaction just before it commits to see whether it has caused any performance issues. It helps us distinguish the overall data from what has just been caused by our application.

The ideal way for application developers to use this view is to add a function call in the application before a commit to track what the transaction has done.

This data can then be inspected so that the output of the current transaction can be distinguished from the overall workload.