Re: Small fix on COPY ON_ERROR document - Mailing list pgsql-hackers

From Masahiko Sawada
Subject Re: Small fix on COPY ON_ERROR document
Date
Msg-id CAD21AoBAAxPdEdDJTwJRQbiQ-+xhfPDcfcPPSddpzTsO9xMLzw@mail.gmail.com
Whole thread Raw
In response to Small fix on COPY ON_ERROR document  (Yugo NAGATA <nagata@sraoss.co.jp>)
Responses Re: Small fix on COPY ON_ERROR document
List pgsql-hackers
On Fri, Jan 26, 2024 at 11:28 AM Yugo NAGATA <nagata@sraoss.co.jp> wrote:
>
> Hi,
>
> I found that the documentation of COPY ON_ERROR said
> COPY stops operation at the first error when
> "ON_ERROR is not specified.", but it also stop when
> ON_ERROR is specified to the default value, "stop".
>
> I attached a very small patch to fix this just for
> making the description more accurate.

Thank you for the patch!

+1 to fix it.

-    <literal>ON_ERROR</literal> is not specified. This
-    should not lead to problems in the event of a <command>COPY
+    <literal>ON_ERROR</literal> is not specified or <literal>stop</literal>.
+    This should not lead to problems in the event of a <command>COPY

How about the followings for consistency with the description of the
ON_ERROR option?

COPY stops operation at the first error if the stop value is specified
to the ON_ERROR option. This should not lead to ...

Regards,

--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com



pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: Remove unused fields in ReorderBufferTupleBuf
Next
From: Richard Guo
Date:
Subject: Re: A performance issue with Memoize