| From: | jian he <jian(dot)universality(at)gmail(dot)com> |
|---|---|
| To: | Jim Jones <jim(dot)jones(at)uni-muenster(dot)de> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp>, torikoshia <torikoshia(at)oss(dot)nttdata(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Change COPY ... ON_ERROR ignore to ON_ERROR ignore_row |
| Date: | 2024-09-12 10:13:00 |
| Message-ID: | CACJufxEgiysa2SMJPGp0aN476Ojm636MfJK88DZC7TVYsXYBBQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Sep 9, 2024 at 10:34 PM Jim Jones <jim(dot)jones(at)uni-muenster(dot)de> wrote:
>
>
> Hi there
>
> On 26.08.24 02:00, jian he wrote:
> > hi all.
> > patch updated.
> > simplified the code a lot.
> >
> > idea is same:
> > COPY t_on_error_null FROM STDIN WITH (on_error set_to_null);
> >
> > If the STDIN number of columns is the same as the target table, then
> > InputFunctionCallSafe
> > call failure will make that column values be null.
> >
> >
> > If the STDIN number of columns is not the same as the target table, then error
> > ERROR: missing data for column \"%s\"
> > ERROR: extra data after last expected column
> > which is status quo.
>
> I wanted to give it another try, but the patch does not apply ...
>
here we are.
please check the attached file.
| Attachment | Content-Type | Size |
|---|---|---|
| v4-0001-on_error-set_to_null.patch | text/x-patch | 11.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andy Fan | 2024-09-12 10:31:41 | Re: Make printtup a bit faster |
| Previous Message | David Rowley | 2024-09-12 10:12:03 | Re: Incremental Sort Cost Estimation Instability |