Re: Moving more work outside WALInsertLock - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Moving more work outside WALInsertLock
Date
Msg-id CA+U5nMJSDTtGu-BR+2bPFa4JQGypiGbgQDshkkhwxN0e_SjZHA@mail.gmail.com
Whole thread Raw
In response to Re: Moving more work outside WALInsertLock  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: Moving more work outside WALInsertLock  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
On Fri, Dec 16, 2011 at 12:07 PM, Heikki Linnakangas
<heikki.linnakangas@enterprisedb.com> wrote:

> 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
> not.

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


pgsql-hackers by date:

Previous
From: Greg Smith
Date:
Subject: Re: Patch to allow users to kill their own queries
Next
From: Heikki Linnakangas
Date:
Subject: Re: Moving more work outside WALInsertLock