Re: Conflict handling for COPY FROM - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Conflict handling for COPY FROM
Date
Msg-id CA+hUKGLfd1x3XkHpN09WRUCvr591pHLS2TvJvzOa60Tuz+LBtg@mail.gmail.com
Whole thread Raw
In response to Re: Conflict handling for COPY FROM  (Surafel Temesgen <surafel3000@gmail.com>)
Responses Re: Conflict handling for COPY FROM  (Anthony Nowocien <anowocien@gmail.com>)
List pgsql-hackers
On Fri, Jul 12, 2019 at 1:42 AM Surafel Temesgen <surafel3000@gmail.com> wrote:
> Here are the patch that contain all the comment given except adding a way to specify
> to ignoring all error because specifying a highest number can do the work and may be
> try to store such badly structure data is a bad idea

Hi Surafel,

FYI GCC warns:

copy.c: In function ‘CopyFrom’:
copy.c:3383:8: error: ‘dest’ may be used uninitialized in this
function [-Werror=maybe-uninitialized]
        (void) dest->receiveSlot(myslot, dest);
        ^
copy.c:2702:16: note: ‘dest’ was declared here
  DestReceiver *dest;
                ^

--
Thomas Munro
https://enterprisedb.com



pgsql-hackers by date:

Previous
From: David Fetter
Date:
Subject: Re: SHOW CREATE
Next
From: Thomas Munro
Date:
Subject: Re: pgbench - implement strict TPC-B benchmark