Re: Additional options for COPY from
| От | Ron Johnson |
|---|---|
| Тема | Re: Additional options for COPY from |
| Дата | |
| Msg-id | CANzqJaABFc15uQp=ORSw066izoe8+v9PpE4HuCUu7wtKryjiuw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Additional options for COPY from (Bryan Sayer <brysayer@gmail.com>) |
| Список | pgsql-general |
On Thu, Sep 25, 2025 at 3:49 PM Bryan Sayer <brysayer@gmail.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!
В списке pgsql-general по дате отправления: