The description of what the per-transaction log file says for skipped
transactions is just plain wrong.
Report and patch by Tomas Vondra, reviewed by Fabien Coelho and
modified by me.
Field schedule_lag> is the difference between the
transaction's scheduled start time, and the time it actually started, in
microseconds. It is only present when the
- The last field skipped_transactions> reports the number of
- transactions skipped because they were too far behind schedule. It is only
- present when both options
- are used.
+ When both
+ the time> for a skipped transaction will be reported as
+ skipped>.