Postgres Pro
Downloads
Home   >   mailing lists

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

From Peter Geoghegan
Subject Re: pgsql: Optimize btree insertions for common case of increasing values
Date
Msg-id CAH2-Wzkekg9G294UnCJfTZAVpO2US_g+-JQqFmcsZW_y5o6Mcg@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Optimize btree insertions for common case of increasingvalues  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: pgsql: Optimize btree insertions for common case of increasingvalues  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
List pgsql-committers
Tree view 
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.

-- 
Peter Geoghegan

pgsql-committers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: pgsql: Optimize btree insertions for common case of increasingvalues
Next
From: Tom Lane
Date:
Subject: pgsql: Fix incorrect close() call in dsm_impl_mmap().