Re: Parallel copy
vignesh C <vignesh21@gmail.com>
From: vignesh C <vignesh21@gmail.com>
To: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Cc: Ashutosh Sharma <ashu.coek88@gmail.com>,
Andres Freund <andres@anarazel.de>, Amit Kapila <amit.kapila16@gmail.com>, Robert Haas <robertmhaas@gmail.com>, Ants Aasma <ants@cybertec.at>, Tomas Vondra <tomas.vondra@2ndquadrant.com>, Alastair Turner <minion@decodable.me>, Thomas Munro <thomas.munro@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2020-07-06T09:27:55Z
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
Attachments
- 0001-Copy-code-readjustment-to-support-parallel-copy.patch (application/x-patch) patch 0001
- 0002-Framework-for-leader-worker-in-parallel-copy.patch (application/x-patch) patch 0002
- 0003-Allow-copy-from-command-to-process-data-from-file-ST.patch (application/x-patch) patch 0003
- 0004-Documentation-for-parallel-copy.patch (application/x-patch) patch 0004
- 0005-Tests-for-parallel-copy.patch (application/x-patch) patch 0005
- 0006-Parallel-Copy-For-Binary-Format-Files.patch (application/x-patch) patch 0006
On Wed, Jul 1, 2020 at 2:46 PM vignesh C <vignesh21@gmail.com> wrote: > > Hi, > > I have made few changes in 0003 & 0005 patch, there were a couple of > bugs in 0003 patch & some random test failures in 0005 patch. > Attached new patches which include the fixes for the same. I have made changes in 0003 patch, to remove changes made in pqmq.c for parallel worker error handling hang issue. This is being discussed in email [1] separately as it is a bug in the head. The rest of the patches have no changes. [1] https://www.postgresql.org/message-id/CALDaNm1d1hHPZUg3xU4XjtWBOLCrA%2B-2cJcLpw-cePZ%3DGgDVfA%40mail.gmail.com Regards, Vignesh EnterpriseDB: http://www.enterprisedb.com