Hi Tom,<br /><br />How much concern is there for the contention for use cases where the WAL can't be bypassed?<br /><br
/>Thanks,Alan<br /><br /><div class="gmail_quote">On Sun, Jun 21, 2009 at 10:00 AM, Tom Lane <span dir="ltr"><<a
href="mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us</a>></span>wrote:<br /><blockquote class="gmail_quote"
style="border-left:1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">Stefan
Kaltenbrunner<stefan@kaltenbrunner.cc> writes:<br /></div><div class="im">> The following copying 3M
rows(each)into a seperate table of the same<br /> > database.<br /><br /></div>Is this with WAL, or bypassing WAL?
Givenwhat we've already seen,<br /> a lot of contention for WALInsertLock wouldn't surprise me much here.<br /> It
shouldbe possible to bypass that though.<br /><br /> regards, tom lane<br /><br /><br
/></blockquote></div><br/>
