From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Scaling XLog insertion (was Re: Moving more work outside WALInsertLock) |
Date: | 2012-02-02 07:46:50 |
Message-ID: | 4F2A3F6A.1020007@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 31.01.2012 17:35, Fujii Masao wrote:
> On Fri, Jan 20, 2012 at 11:11 PM, Heikki Linnakangas
> <heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
>> On 20.01.2012 15:32, Robert Haas wrote:
>>>
>>> On Sat, Jan 14, 2012 at 9:32 AM, Heikki Linnakangas
>>> <heikki(dot)linnakangas(at)enterprisedb(dot)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
Attachment | Content-Type | Size |
---|---|---|
xloginsert-scale-7.patch | text/x-diff | 94.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Kyotaro HORIGUCHI | 2012-02-02 07:51:37 | Re: Speed dblink using alternate libpq tuple storage |
Previous Message | Dmitriy Igrishin | 2012-02-02 07:33:24 | unsigned and signed chars in libpq API |