Incident brief
COPY: extra data after last column
COPY fails when an input row has more fields than the target column list expects; a three-field, tab-separated line loaded into a narrower target raises this bad-copy-format error.
In 10 seconds
- What
- COPY: extra data after last column
- What triggers it
- Run COPY into a table (or column list) with fewer columns than the input row provides.
- The fix
- Make the column list match the number of fields in each input row.
- Proof
- Reproduced on PostgreSQL 18.4 → A single COPY reproduces SQLSTATE 22P04; the row with an extra tab-separated field is rejected and the line is echoed in the CONTEXT.
The fix
What to do right now
The immediate, application-level response to this error.
- Make the column list match the number of fields in each input row.
- Fix the delimiter or the file so rows have exactly as many fields as target columns; use an explicit COPY (col1, col2, ...) list.
-- Match the COPY column list to the number of fields per row.
COPY copy_target (a, b) FROM STDIN;
1 2
\.Diagnose
See it live on the server
Run these against the affected instance to confirm the diagnosis before you act.
Standard triage — not specific to this error
These are canonical PostgreSQL system-catalog queries, shown as SQL to run. No sample output is attached because this is general triage, not a captured lab transcript.This SQLSTATE does not have an error-specific live snapshot yet. These are the canonical system-catalog queries you run against the affected server to see the problem in real time — standard triage, not a reproduced transcript.
What is running right now
Active backends, how long each has been running, and what it is waiting on.
SELECT pid,
state,
wait_event_type,
wait_event,
now() - query_start AS running_for,
left(query, 80) AS query
FROM pg_stat_activity
WHERE state <> 'idle'
AND pid <> pg_backend_pid()
ORDER BY running_for DESC NULLS LAST;Who is blocking whom
Turn raw blocking PIDs into the actual queries on both sides of the wait.
SELECT blocked.pid AS blocked_pid,
blocked.query AS blocked_query,
blocking.pid AS blocking_pid,
blocking.query AS blocking_query
FROM pg_stat_activity AS blocked
JOIN LATERAL unnest(pg_blocking_pids(blocked.pid)) AS b(pid) ON true
JOIN pg_stat_activity AS blocking ON blocking.pid = b.pid
WHERE cardinality(pg_blocking_pids(blocked.pid)) > 0;Locks that are still waiting
Every lock a backend has requested but not yet been granted.
SELECT l.pid,
l.locktype,
l.mode,
l.granted,
COALESCE(c.relname, l.transactionid::text) AS object
FROM pg_locks l
LEFT JOIN pg_class c ON c.oid = l.relation
WHERE NOT l.granted
ORDER BY l.pid;Why it happens
What PostgreSQL is telling you
The mechanism behind the error, grounded in the official manual — not paraphrased.
PostgreSQL 18 Documentation — Appendix A. PostgreSQL Error Codes (Table A.1, Class 22 — Data Exception)
22P04 → bad_copy_file_formatRead the full section on postgresql.org →
Loading a row with too many fields
The input line has three tab-separated fields but the target expects fewer, so COPY raises 'extra data after last expected column'.The session continues normally
The failing statement ran outside a transaction block, so nothing was left in a bad state — the next statement in the same connection runs normally.Reproduce & verify
A real, single-session PostgreSQL reproduction
A literal transcript of SQL run against a live PostgreSQL instance in an isolated lab — the commands below are exactly what was executed.
- 1Run COPY into a table (or column list) with fewer columns than the input row provides.
- 2PostgreSQL parses the row and finds an extra delimited field after the last expected column.
- 3The load aborts with SQLSTATE 22P04 and echoes the offending line in the CONTEXT.
An import job received a file with an unexpected extra column and every row failed COPY until the layout was reconciled.
CREATE TABLE copy_target(a int, b int);COPY copy_target (a, b) FROM STDIN;
1 2 3
\.SELECT 'ok' AS session_after_error;What PostgreSQL actually returned
CREATE TABLEERROR: extra data after last expected column
CONTEXT: COPY copy_target, line 1: "1 2 3" session_after_error
---------------------
ok
(1 row)The same COPY succeeds once the row width matches the target columns.
We run a COPY whose row width matches the column list to show a clean load.
Without this
Before: an extra field aborts the load
With this, tested
After: the matching row loads
What Pro unlocks here
- The exact prevention SQL — copy-paste ready
- Raw psql output captured from the Docker lab
- A senior-DBA action list to take it further
- Live monitoring queries to catch it in production
- The deeper audit: fix-that-fails counterexample, GUC before/after, server-log evidence
Related & next steps
Follow the thread
Everything this error touches — jump straight to the sibling error, term, runbook, or parameter.
Verification
- Last verified
- 2026-07-24 (isolated lab, PostgreSQL 18.4)
- Reviewed by
- Verified against PostgreSQL 18.4 in an isolated lab environment
- Audit status
- reviewed