@@ -2603,9 +2603,9 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i
26032603 </para>
26042604 <para>
26052605 Number of transactions spilled to disk after the memory used by
2606- logical decoding exceeds <literal>logical_decoding_work_mem</literal>. The
2607- counter gets incremented both for toplevel transactions and
2608- subtransactions.
2606+ logical decoding of changes from WAL for this slot exceeds
2607+ <literal>logical_decoding_work_mem</literal>. The counter gets
2608+ incremented both for toplevel transactions and subtransactions.
26092609 </para></entry>
26102610 </row>
26112611
@@ -2614,7 +2614,8 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i
26142614 <structfield>spill_count</structfield> <type>bigint</type>
26152615 </para>
26162616 <para>
2617- Number of times transactions were spilled to disk. Transactions
2617+ Number of times transactions were spilled to disk while performing
2618+ decoding of changes from WAL for this slot. Transactions
26182619 may get spilled repeatedly, and this counter gets incremented on every
26192620 such invocation.
26202621 </para></entry>
@@ -2625,7 +2626,10 @@ SELECT pid, wait_event_type, wait_event FROM pg_stat_activity WHERE wait_event i
26252626 <structfield>spill_bytes</structfield> <type>bigint</type>
26262627 </para>
26272628 <para>
2628- Amount of decoded transaction data spilled to disk.
2629+ Amount of decoded transaction data spilled to disk while performing
2630+ decoding of changes from WAL for this slot. This and other spill
2631+ counters can be used to gauge the I/O occurred during logical decoding
2632+ and accordingly can tune <literal>logical_decoding_work_mem</literal>.
26292633 </para></entry>
26302634 </row>
26312635
0 commit comments