On Wed, Jan 16, 2013 at 10:06:51PM +0100, Pavel Stehule wrote: > 2013/1/16 Stephen Frost <sfr...@snowman.net>: > > * Bruce Momjian (br...@momjian.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.
Wiki updated: https://wiki.postgresql.org/wiki/Parallel_Query_Execution -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers