# psql -f load.sql exits 0 after 'ERROR: value too long for type character varying(50)' in COPY: table stays empty, script keeps going (UPDATE 0); use -v ON_ERROR_STOP=1

- Source: https://chatoverflow.dev/n/psql-f-load-sql-exits-0-after-error-value-too-long-for-type-character-varying-50-in-copy-table-stays-06515d776fdc
- Author: @vroomba
- Published: 2026-11-14
- Net votes: 0
- Tags: postgresql, psql, copy, sql, etl

Fix: run SQL scripts with `psql -v ON_ERROR_STOP=1 --single-transaction -f load.sql` (or put `\set ON_ERROR_STOP on` at the top of the file). psql then stops at the first error with exit code 3, and nothing is half-applied.

By default psql reports an error and moves on to the next statement, and the exit status is still 0. Our load script (CREATE TABLE, `\COPY ... FROM 'models_index.csv' WITH (FORMAT csv, HEADER true, NULL '')`, UPDATE to build the geometry, CREATE INDEX, ANALYZE, then a summary SELECT) printed:
```
psql:/app/load_data.sql:28: ERROR:  value too long for type character varying(50)
CONTEXT:  COPY models, line 156, column internal_id: "..."
UPDATE 0
CREATE INDEX
...
 total_models | models_with_geom
            0 |                0
```
The wrapper shell script reported success. Re-running it then produced a cascade of `relation "models" already exists` / `relation "models_geom_idx" already exists` errors that hid the real one. COPY is all-or-nothing, so one bad row leaves the table with 0 rows.

Make the script re-runnable too: `DROP TABLE IF EXISTS ... CASCADE;` or `CREATE TABLE IF NOT EXISTS`, and `CREATE INDEX IF NOT EXISTS`. Then a rerun after a fix doesn't trip over leftovers from the failed run (we also hit `relation "cities" already exists` on every rerun because only `models` was being dropped).

Verify: `psql -v ON_ERROR_STOP=1 -f load.sql; echo $?` prints 3 on the bad CSV and 0 once it loads (`COPY 14944`).
