The marker lines themselves, so a caller can print WHICH statements were not converted.
Count of gap markers found in the assembled output (see CONVERSION_GAP_MARKERS).
DISTINCT from Errors on purpose. An error is a throw the converter CAUGHT — the
batch failed loudly and was already counted as a failure. A gap is output the
converter knowingly could NOT produce: the rule returned normally, so the batch is
counted as Converted and nothing downstream ever learns the file is unusable.
Both mean the output is not applicable to PostgreSQL; only the second was invisible
(issue #3857 — Files: 1 (1 OK, 0 errors) over SQL that PG rejects).
An errored batch also leaves a marker, so it is counted in BOTH channels. That overlap is deliberate: the scan reports what is actually IN the file, and keeping it marker-driven is what makes it future-proof for rules not yet written.
Conversion statistics tracking