Keep the lesson for the next incident
Record the row-selection rule
Document how the importer determines header presence, handles introductory lines, and chooses the first data record. State when users can override inference. Keep these rules together so a future change to skipping lines does not silently alter header handling or the expected record count.
Retain an ambiguous first row
Preserve a sanitized all-text or label-like first record that exposed the issue. Pair it with an actual header and expected record identities. Explain which row should name fields and which should remain data so the fixture remains useful after labels or parser libraries change.
Review newly supported layouts
Assign a review when another export producer, preamble format, or header selection control is introduced. Compare preview and execution against the same fixture. Track confirmed missing-first-record incidents separately from generic validation failures where possible, since successful imports can otherwise conceal the recurrence.
What to carry forward
Close follow-up with a clear row-selection contract, a discriminating fixture, and a named review owner. Preserve any source-format limitation in the import guidance. The next maintainer should be able to explain the first imported record without relying on what the detector happened to infer that day.
Technical background: PostgreSQL documentation.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow