Re: lock contention on parallel COPY ? - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: lock contention on parallel COPY ?
Date
Msg-id 48DD0A38.7000402@dunslane.net
Whole thread Raw
In response to Re: lock contention on parallel COPY ?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: lock contention on parallel COPY ?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers

Tom Lane wrote:
> Stefan Kaltenbrunner <stefan@kaltenbrunner.cc> writes:
>   
>> samples  %        symbol name
>> 1933314  21.8884  LWLockAcquire
>> 1677808  18.9957  XLogInsert
>> 848227    9.6034  LWLockRelease
>> 414179    4.6892  DoCopy
>> 332633    3.7660  CopyReadLine
>> 266580    3.0181  UnpinBuffer
>> 221693    2.5099  heap_formtuple
>>     
>
> I suppose Andrew didn't yet put in the hack to avoid WAL logging
> during the COPY commands.  The LWLockAcquires are presumably
> blocking on WALInsertLock, given that XLogInsert is also right
> up there ...
>
>             
>   


Yes I did. That's what the --truncate-before-load switch does (or should 
do).

cheers

andrew


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: lock contention on parallel COPY ?
Next
From: Tom Lane
Date:
Subject: Re: lock contention on parallel COPY ?