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

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, 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 19:46:49
Message-ID: CAH2-Wz=EEQv6fUpj4HGR+uFpJ8k3vzR2BwfZ1QOw7ORcjfxnTg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Tue, Apr 10, 2018 at 12:30 PM, Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
>> Apart from that, other changes requested are included in the patch. This
>> also takes care of Heikki's observation regarding UNLOGGED tables on the
>> other thread.
>
> Cool.

BTW, Heikki's commit didn't remove the "no split is in progress" part
of the top comment. I think that you can remove that now, but leave in
the separate P_INCOMPLETE_SPLIT() assertion that you've proposed.

--
Peter Geoghegan

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2018-04-10 20:15:19 pgsql: Put back parallel-safety guards in plpython and src/test/regress
Previous Message Peter Geoghegan 2018-04-10 19:30:27 Re: pgsql: Optimize btree insertions for common case of increasing values