Heikki Linnakangas wrote:
> Greg Stark wrote:
>> On Fri, Aug 28, 2009 at 8:07 PM, Simon Riggs<simon(at)2ndquadrant(dot)com> wrote:
>>> WALInsertLock is heavily contended and likely always will be even if we
>>> apply some of the planned fixes.
>> I've lost any earlier messages, could you resend the raw data on which
>> this is based?
> I don't have any pointers right now, but WALInsertLock does often show
> up as a bottleneck in write-intensive benchmarks.
yeah I recently ran accross that issue with testing concurrent COPY
and (iirc) also here:
however the general issue is easily visible in almost any write
intensive concurrent workload on a fast IO subsystem(ie
In response to
pgsql-hackers by date
|Next:||From: Jan Otto||Date: 2009-08-30 10:35:58|
|Subject: Re: drop tablespace error: invalid argument|
|Previous:||From: Heikki Linnakangas||Date: 2009-08-30 06:03:23|
|Subject: Re: LWLock Queue Jumping|