Re: Add new COPY option REJECT_LIMIT
От | Fujii Masao |
---|---|
Тема | Re: Add new COPY option REJECT_LIMIT |
Дата | |
Msg-id | fab7018f-6e00-4be4-bd1e-4a013096f6c9@oss.nttdata.com обсуждение исходный текст |
Ответ на | Add new COPY option REJECT_LIMIT (torikoshia <torikoshia@oss.nttdata.com>) |
Ответы |
Re: Add new COPY option REJECT_LIMIT
|
Список | pgsql-hackers |
On 2024/01/26 18:49, torikoshia wrote: > Hi, > > 9e2d870 enabled the COPY command to skip soft error, and I think we can add another option which specifies the maximumtolerable number of soft errors. > > I remember this was discussed in [1], and feel it would be useful when loading 'dirty' data but there is a limit to howdirty it can be. > > Attached a patch for this. > > What do you think? The patch no longer applies cleanly to HEAD. Could you update it? I think the REJECT_LIMIT feature is useful. Allowing it to be set as either the absolute number of skipped rows or a percentageof the total input rows is a good idea. However, if we support REJECT_LIMIT, I'm not sure if the ON_ERROR option is still necessary. REJECT_LIMIT seems to coverthe same cases. For instance, REJECT_LIMIT=infinity can act like ON_ERROR=ignore, and REJECT_LIMIT=0 can act like ON_ERROR=stop. Therefore, having both ON_ERROR and REJECT_LIMIT might be confusing. Regards, -- Fujii Masao Advanced Computing Technology Center Research and Development Headquarters NTT DATA CORPORATION
В списке pgsql-hackers по дате отправления: