| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Mike Blackwell <mike(dot)blackwell(at)rrd(dot)com> |
| Cc: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, Alastair Turner <minion(at)decodable(dot)me>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Parallel copy |
| Date: | 2020-02-19 04:23:48 |
| Message-ID: | CAA4eK1+isn3Akjer9=HVcTeyGvdbb-EG1AdUT+VX=FppmatDKg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Feb 18, 2020 at 7:51 PM Mike Blackwell <mike(dot)blackwell(at)rrd(dot)com>
wrote:
> On Sun, Feb 16, 2020 at 12:51 AM Andrew Dunstan <
> andrew(dot)dunstan(at)2ndquadrant(dot)com> wrote:
>
>>
>> IIRC, in_quote only matters here in CSV mode (because CSV fields can
>> have embedded newlines). So why not just forbid parallel copy in CSV
>> mode, at least for now? I guess it depends on the actual use case. If we
>> expect to be parallel loading humungous CSVs then that won't fly.
>
>
> Loading large CSV files is pretty common here. I hope this can be
> supported.
>
>
Thank you for your inputs. It is important and valuable.
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2020-02-19 04:28:04 | Re: Print physical file path when checksum check fails |
| Previous Message | Amit Kapila | 2020-02-19 04:22:11 | Re: Parallel copy |