Re: Additional options for COPY from

From: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
To: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Additional options for COPY from
Date: 2025-09-25 20:08:34
Message-ID: CANzqJaABFc15uQp=ORSw066izoe8+v9PpE4HuCUu7wtKryjiuw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Sep 25, 2025 at 3:49 PM Bryan Sayer <brysayer(at)gmail(dot)com> wrote:

> Hi,
>
> I'm not sure if this is the best list to ask this (and I am very new to
> PostgreSQL) but I think more options are needed in the COPY from command,
> in order to better deal with exceptions. By exceptions I mean data not
> consistent with the format, empty rows, extra delimiters at the end of
> rows, etc.
>

PG 17 COPY has ON_ERROR.

> Is there someone or a party that deals with the details of the COPY
> command that I could discuss this with?
>
> Just for context, I am dealing with delimited data of millions of rows and
> perhaps 60 columns or so that I wish to read into tables in a Postgres 17
> database under Windows 11, with everything on local drives.
>
COPY is pretty simplistic. 3rd party CSV loaders like pgloader and
pg_bulkload exist for that reason. And there's always Python & Perl for
when your data is really dirty.

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Brent Wood 2025-09-25 20:10:39 Re: Additional options for COPY from
Previous Message Adrian Klaver 2025-09-25 19:13:12 Re: Compatibility Informations