Re: Re: [COMMITTERS] pgsql: Reduce WAL activity for page splits: > Currently, an index split - Mailing list pgsql-hackers

From Stefan Kaltenbrunner
Subject Re: Re: [COMMITTERS] pgsql: Reduce WAL activity for page splits: > Currently, an index split
Date
Msg-id 45CAF558.5030408@kaltenbrunner.cc
Whole thread Raw
In response to Re: Re: [COMMITTERS] pgsql: Reduce WAL activity for page splits: > Currently, an index split  (Heikki Linnakangas <heikki@enterprisedb.com>)
List pgsql-hackers
Heikki Linnakangas wrote:
> Stefan Kaltenbrunner wrote:
>> Bruce Momjian wrote:
>>> Log Message:
>>> -----------
>>> Reduce WAL activity for page splits:
>>>
>>>> Currently, an index split writes all the data on the split page to
>>>> WAL. That's a lot of WAL traffic. The tuples that are copied to the
>>>> right page need to be WAL logged, but the tuples that stay on the
>>>> original page don't.
>>
>>
>> this patch killed both of my OpenBSD buildfarm members
> 
> lopaque was referenced after pfreeing the temp page it pointed to. Also 
> later in the function the LSN of the left page was set, but again using 
> a pointer to the pfreed temp copy instead of the real shared memory buffer.
> 
> Here's a fix.

confirmed - with that patch -HEAD passes a full regression test run at 
least on emu.


Stefan


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Reduce WAL activity for page splits: > Currently, an index split
Next
From: Markus Schiltknecht
Date:
Subject: compilation of pg_config fails