Re: Parallel copy

Amit Kapila <amit.kapila16@gmail.com>

From: Amit Kapila <amit.kapila16@gmail.com>

To: Mike Blackwell <mike.blackwell@rrd.com>

Cc: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>, Alastair Turner <minion@decodable.me>, Thomas Munro <thomas.munro@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2020-02-19T04:23:48Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Allow WaitLatch() to be used without a latch.
- 733fa9aa51c5 14.0 cited
Add %P to log_line_prefix for parallel group leader
- b8fdee7d0ca8 14.0 cited
Include replication origins in SQL functions for commit timestamp
- b1e48bbe64a4 14.0 cited
Avoid useless buffer allocations during binary COPY FROM.
- cd22d3cdb9bd 14.0 cited

On Tue, Feb 18, 2020 at 7:51 PM Mike Blackwell <mike.blackwell@rrd.com>
wrote:

> On Sun, Feb 16, 2020 at 12:51 AM Andrew Dunstan <
> andrew.dunstan@2ndquadrant.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