| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Parallel copy |
| Date: | 2020-02-20 10:41:39 |
| Message-ID: | CAA4eK1KqQ_NnUvv9n=pM_b-zQPei4p=S5FWoPoZoxn-N7tkkhg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Feb 20, 2020 at 5:12 AM David Fetter <david(at)fetter(dot)org> wrote:
>
> On Fri, Feb 14, 2020 at 01:41:54PM +0530, Amit Kapila wrote:
> > This work is to parallelize the copy command and in particular "Copy
> > <table_name> from 'filename' Where <condition>;" command.
>
> Apropos of the initial parsing issue generally, there's an interesting
> approach taken here: https://github.com/robertdavidgraham/wc2
>
Thanks for sharing. I might be missing something, but I can't figure
out how this can help here. Does this in some way help to allow
multiple workers to read and tokenize the chunks?
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2020-02-20 11:09:25 | Re: Add PostgreSQL home page to --help output |
| Previous Message | Dmitry Dolgov | 2020-02-20 10:39:45 | Re: Experimenting with transactional memory for SERIALIZABLE |