Re: Enabling B-Tree deduplication by default

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Subject: Re: Enabling B-Tree deduplication by default
Date: 2020-01-30 22:18:14
Message-ID: CAH2-WznoUZGrWAq98+bquKad8G9XyioeU7_g-G8acapekKp83g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jan 30, 2020 at 2:13 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> My approach to showing the downsides of the patch wasn't particularly
> obvious, or easy to come up with. I could have contrived a case like
> the insert benchmark, but with more low cardinality non-unique
> indexes.

Sorry. I meant with more *high* cardinality indexes. An exaggerated
version of the original insert benchmark.

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2020-01-30 22:35:53 Re: Parallel CREATE INDEX vs DSM starvation
Previous Message Peter Geoghegan 2020-01-30 22:13:43 Re: Enabling B-Tree deduplication by default