Skip site navigation (1) Skip section navigation (2)

Re: Parallel query execution

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 (view raw or flat)
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


In response to

Responses

pgsql-hackers by date

Next:From: Dimitri FontaineDate: 2013-01-16 21:16:03
Subject: Re: Event Triggers: adding information
Previous:From: Bruce MomjianDate: 2013-01-16 20:45:46
Subject: Re: CF3+4

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group