Re: POC PATCH: copy from ... exceptions to: (was Re: VLDB Features)
От | torikoshia |
---|---|
Тема | Re: POC PATCH: copy from ... exceptions to: (was Re: VLDB Features) |
Дата | |
Msg-id | 9a94e684d6528dff74de5959e97032f3@oss.nttdata.com обсуждение исходный текст |
Ответ на | Re: POC PATCH: copy from ... exceptions to: (was Re: VLDB Features) (Daniel Gustafsson <daniel@yesql.se>) |
Ответы |
Re: POC PATCH: copy from ... exceptions to: (was Re: VLDB Features)
|
Список | pgsql-hackers |
On 2023-03-07 18:09, Daniel Gustafsson wrote: >> On 7 Mar 2023, at 09:35, Damir Belyalov <dam.bel07@gmail.com> wrote: > >> I felt just logging "Error: %ld" would make people wonder the meaning >> of >> the %ld. Logging something like ""Error: %ld data type errors were >> found" might be clearer. >> >> Thanks. For more clearance change the message to: "Errors were found: >> %". > > I'm not convinced that this adds enough clarity to assist the user. We > also > shouldn't use "error" in a WARNING log since the user has explicitly > asked to > skip rows on error, so it's not an error per se. +1 > How about something like: > > ereport(WARNING, > (errmsg("%ld rows were skipped due to data type > incompatibility", cstate->ignored_errors), > errhint("Skipped rows can be inspected in the database log > for reprocessing."))); Since skipped rows cannot be inspected in the log when log_error_verbosity is set to terse, it might be better without this errhint. -- Regards, -- Atsushi Torikoshi NTT DATA CORPORATION
В списке pgsql-hackers по дате отправления: