2011/8/28 pasman pasmański <pasman(dot)p(at)gmail(dot)com>:
> Pity that this patch works only on hpux :(.
Well, not really. x86 is already well-behaved. On a 32-core x86 box
running Linux, performs seems to plateau and level off, and then fall
off gradually. But on ia64, performance just collapses after about 24
cores. The fact that we don't have that problem everywhere is a good
thing, not a bad thing...
> But i have an idea: maybe when executor stop at locked row, it should
> process next row instead of wait.
> Of course if query not contain "order by" or windowing functions.
That wouldn't really help, first of all because you'd then have to
remember to go back to that row (and chances are it would still be
contended then), and second because these aren't row-level locks
anyway. They're locks on various global data structures, such as the
The Enterprise PostgreSQL Company
In response to
pgsql-hackers by date
|Next:||From: YAMAMOTO Takashi||Date: 2011-08-29 00:28:34|
|Subject: Re: tab stop in README|
|Previous:||From: Tom Lane||Date: 2011-08-29 00:00:05|
|Subject: Re: spinlocks on HP-UX |