Re: Scaling XLog insertion (was Re: Moving more work outside WALInsertLock)

Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>

From: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
To: Fujii Masao <masao.fujii@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2012-02-02T07:46:50Z
Lists: pgsql-hackers

Attachments

On 31.01.2012 17:35, Fujii Masao wrote:
> On Fri, Jan 20, 2012 at 11:11 PM, Heikki Linnakangas
> <heikki.linnakangas@enterprisedb.com>  wrote:
>> On 20.01.2012 15:32, Robert Haas wrote:
>>>
>>> On Sat, Jan 14, 2012 at 9:32 AM, Heikki Linnakangas
>>> <heikki.linnakangas@enterprisedb.com>    wrote:
>>>>
>>>> Here's another version of the patch to make XLogInsert less of a
>>>> bottleneck
>>>> on multi-CPU systems. The basic idea is the same as before, but several
>>>> bugs
>>>> have been fixed, and lots of misc. clean up has been done.
>>>
>>>
>>> This seems to need a rebase.
>>
>>
>> Here you go.
>
> The patch seems to need a rebase again.

Here you go again. It conflicted with the group commit patch, and the 
patch to WAL-log and track changes to full_page_writes setting.

-- 
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com