| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Parallel query execution |
| Date: | 2013-01-16 21:06:51 |
| Message-ID: | CAFj8pRAgzThWZn5A4YjskcJAUjkB3GJ=5dnYq+FvnqPbD5A-AQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2013/1/16 Stephen Frost <sfrost(at)snowman(dot)net>:
> * Bruce Momjian (bruce(at)momjian(dot)us) wrote:
>> I am not sure how a COPY could be easily parallelized, but I supposed it
>> could be done as part of the 1GB segment feature. People have
>> complained that COPY is CPU-bound, so it might be very interesting to
>> see if we could offload some of that parsing overhead to a child.
>
> COPY can certainly be CPU bound but before we can parallelize that
> usefully we need to solve the problem around extent locking when trying
> to do multiple COPY's to the same table.
Probably update any related indexes and constraint checking should be
paralellized.
Regards
Pavel
>
> Thanks,
>
> Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2013-01-16 21:16:03 | Re: Event Triggers: adding information |
| Previous Message | Bruce Momjian | 2013-01-16 20:45:46 | Re: CF3+4 |