| From: | rob stone <floriparob(at)tpg(dot)com(dot)au> |
|---|---|
| To: | Brent Wood <brent(dot)wood(at)earthsciences(dot)nz> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Using \copy to populate a table |
| Date: | 2026-03-17 12:08:29 |
| Message-ID: | 327a4bfde1f1c55e50d0436c0f6dceb41e4afc75.camel@tpg.com.au |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, 2026-03-15 at 07:21 +0000, Brent Wood wrote:
>
>
>
> Have you tried explicitly specifying the string to represent null
> values?
>
>
> COPY table_name FROM 'path/to/file' WITH (FORMAT text, NULL 'null');
> -- Or the older syntax:
> COPY table_name FROM 'path/to/file' WITH DELIMITER ',' NULL AS
> 'null';
>
>
Hello,
I took on board Adrian's suggestion and went back to the source and had
the file recreated and it has now been loaded successfully.
Cheers,
Rob
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shaheed Haque | 2026-03-17 13:58:32 | Can I use pg_dump to save a sequence for a table that is not also being saved? |
| Previous Message | Peter Kleiner | 2026-03-17 02:16:26 | Re: Using \copy to populate a table |