Postgres Pro
Downloads
Home   >   mailing lists

Re: pgsql: Optimize btree insertions for common case of increasingvalues - Mailing list pgsql-committers

From Andrew Dunstan
Subject Re: pgsql: Optimize btree insertions for common case of increasingvalues
Date
Msg-id d43ca132-132a-709f-cb44-ed913f68067f@2ndQuadrant.com
Whole thread Raw
In response to Re: pgsql: Optimize btree insertions for common case of increasing values  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: pgsql: Optimize btree insertions for common case of increasing values
List pgsql-committers
Tree view 

On 04/10/2018 06:33 PM, Peter Geoghegan wrote:
> On Tue, Apr 10, 2018 at 3:27 PM, Andrew Dunstan <andrew@dunslane.net> wrote:
>> Committed with light editing. I didn't put the #define in the .h file -
>> it's only used here and that seemed like unnecessary clutter. I moved it
>> to the top of the file. I also standardized the spelling of "optimization".
> The comments still say "Check if the page...no split is in progress".
> Despite the fact that that's just an assertion now.
>

Fixed.

cheers

andrew

-- 
Andrew Dunstan                https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-committers by date:

Previous
From: Andrew Dunstan
Date:
Subject: pgsql: minor comment fixes in nbtinsert.c
Next
From: Peter Geoghegan
Date:
Subject: Re: pgsql: Optimize btree insertions for common case of increasing values