Re: pgsql: Optimize btree insertions for common case of increasing values

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, pgsql-committers <pgsql-committers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: Optimize btree insertions for common case of increasing values
Date: 2018-04-10 22:39:46
Message-ID: CAH2-Wznq14xxv+upm56xBJ89dYjkF4JtHUZcmEoNpZuoOnR2GA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Tue, Apr 10, 2018 at 3:37 PM, Andrew Dunstan
<andrew(dot)dunstan(at)2ndquadrant(dot)com> wrote:
>> The comments still say "Check if the page...no split is in progress".
>> Despite the fact that that's just an assertion now.
>>
>
> Fixed.

Thanks.

--
Peter Geoghegan

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2018-04-11 00:10:58 Re: pgsql: Validate page level checksums in base backups
Previous Message Andrew Dunstan 2018-04-10 22:37:54 Re: pgsql: Optimize btree insertions for common case of increasing values