You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
Currently, the Trace API doesn't have any support for generating trace events when a sweep happens (starts/finishes). In the trace output, there should be a way to distinguish between a sweep, which has been triggered automatically (due to the sweep interval) and a sweep, which was invoked by the user manually.
c) SWEEP_FAILED - when sweep process was failed (due to shutdown or on-disk error, etc)
Prints usual attachment info and performance counters. Transaction counters are not printed.
Note: failure reason is not printed, use log_errors parameter to obtain this info.
d) SWEEP_PROGRESS - put after processing of every non-empty relation
Prints usual attachment info and performance counters. Performance stats is reset after beign printed to
allow see separate stats for every relation (i.e. stats in this event is not accumulated during whole sweep
Note: some metadata related activity could be present at stats.
- all sweep events are put before ATTACH_DATABASE event.
- auto-triggered sweep could be distinguished from manual-started sweep by user name at attachment info.
For auto-triggered sweep it will be SWEEPER.