| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Damir <dam(dot)bel07(at)gmail(dot)com>, torikoshia <torikoshia(at)oss(dot)nttdata(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>, daniel(at)yesql(dot)se, anisimow(dot)d(at)gmail(dot)com, HukuToc(at)gmail(dot)com, Andrey Lepikhov <a(dot)lepikhov(at)postgrespro(dot)ru>, Alena Rybakina <lena(dot)ribackina(at)yandex(dot)ru> |
| Subject: | Re: POC PATCH: copy from ... exceptions to: (was Re: VLDB Features) |
| Date: | 2023-11-09 00:26:00 |
| Message-ID: | 20231109002600.fuihn34bjqqgmbjm@awork3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2023-11-08 19:00:01 -0500, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > On 2023-11-08 13:18:39 -0500, Tom Lane wrote:
> >> I think an actually usable feature of this sort would involve
> >> copying all the failed lines to some alternate output medium,
> >> perhaps a second table with a TEXT column to receive the original
> >> data line.
>
> > If we go in that direction, we should make it possible to *not* use such a
> > table as well, for some uses it'd be pointless.
>
> Why? You can always just drop the errors table if you don't want it.
I think it'll often just end up littering the database, particularly if the
callers don't care about a few errors.
> But I fail to see the use-case for ignoring errors altogether.
My experience is that there's often a few errors due to bad encoding, missing
escaping etc that you don't care sufficiently about when importing large
quantities of data.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Damir Belyalov | 2023-11-09 00:28:25 | Re: POC PATCH: copy from ... exceptions to: (was Re: VLDB Features) |
| Previous Message | Tom Lane | 2023-11-09 00:00:01 | Re: POC PATCH: copy from ... exceptions to: (was Re: VLDB Features) |