On Fri, Dec 16, 2011 at 12:07 PM, Heikki Linnakangas
> Anyway, I'm looking at ways to make the memcpy() of the payload happen
> without the lock, in parallel, and once you do that the record header CRC
> calculation can be done in parallel, too. That makes it irrelevant from a
> performance point of view whether the prev-link is included in the CRC or
Better plan. So we keep the prev link in the CRC.
I already proposed a design for that using page-level share locks any
reason not to go with that?
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
In response to
pgsql-hackers by date
|Next:||From: Heikki Linnakangas||Date: 2011-12-16 12:50:24|
|Subject: Re: Moving more work outside WALInsertLock|
|Previous:||From: Greg Smith||Date: 2011-12-16 12:31:39|
|Subject: Re: Patch to allow users to kill their own queries|