Re: [HACKERS] GSOC'17 project introduction: Parallel COPY execution with errors handling

Thank you for your comments Peter, there are some points that I did not think about before.On 9 Jun 2017, at 01:09, Peter Geoghegan wrote:Adding a full support of ON CONFLICT DO NOTHING/UPDATE to COPY seemsto be a large separated task and is out of the current project scope,

Re: [HACKERS] GSOC'17 project introduction: Parallel COPY execution with errors handling

Yes, sure, I don't doubt it. The question was around step 4 in the following possible algorithm: 1. Suppose we have to insert N records 2. Start subtransaction with these N records 3. Error is raised on k-th line 4. Then, we know that we can safely insert all lines from the 1st till (k - 1) 5.

Re: [HACKERS] GSOC'17 project introduction: Parallel COPY execution with errors handling

e glad to receive any critical remarks and suggestions. Alexey > On 23 Mar 2017, at 17:24, Stas Kelvich <stas.kelv...@gmail.com> wrote: > >> >> On 23 Mar 2017, at 15:53, Craig Ringer <cr...@2ndquadrant.com> wrote: >> >> On 23 March 2017 at 19:33, Alexey K

[HACKERS] GSOC'17 project introduction: Parallel COPY execution with errors handling

Hi pgsql-hackers, I'm planning to apply to GSOC'17 and my proposal consists currently of two parts: (1) Add errors handling to COPY as a minimum program Motivation: Using PG on the daily basis for years I found that there are some cases when you need to load (e.g. for a further analytics) a