Feedback-ID: i76984098:Fastmail
Message-ID: <c7b85d55-e5bb-4677-84f9-d560b6c21285@aklaver.com>
Date: Sat, 1 Mar 2025 08:31:08 -0800
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Please implement a catch-all error handler per row, for COPY
To: me nefcanto <sn.1361@gmail.com>, pgsql-general@lists.postgresql.org
References: <CAEHBEOCqqkSitU5gx=8aHD3ZeLtRy-1eC=Xs=xB-thFNR9JpYA@mail.gmail.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <CAEHBEOCqqkSitU5gx=8aHD3ZeLtRy-1eC=Xs=xB-thFNR9JpYA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/c7b85d55-e5bb-4677-84f9-d560b6c21285%40aklaver.com>
Precedence: bulk

On 3/1/25 07:18, me nefcanto wrote:
> Hello
> 
>
> All of these scenarios are such that data sanitation is difficult if not 
> possible before doing the bulk operation (copy).
> 
> I realized that when we specify `on_error ignore` it just handles a 
> handful of errors. I thought this was a bug and sent an email to the 
> pgsql-bugs maling list. But they said it's the intended behavior.
> 

Take a look at:

http://ossc-db.github.io/pg_bulkload/index.html

and

https://pgloader.io/

They may be able to meet your needs.

> 
> Regards
> Saeed

-- 
Adrian Klaver
adrian.klaver@aklaver.com