Re: [HACKERS] [WIP] Effective storage of duplicates in B-tree index.

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [HACKERS] [WIP] Effective storage of duplicates in B-tree index.
Date: 2019-11-13 19:33:38
Message-ID: CA+TgmoY=yti_sJu-wdT+U1Pe1=EpPD3Xp94CY5M0Gpft2vXGFw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Nov 12, 2019 at 6:22 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> * Disabled deduplication in system catalog indexes by deeming it
> generally unsafe.

I (continue to) think that deduplication is a terrible name, because
you're not getting rid of the duplicates. You are using a compressed
representation of the duplicates.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2019-11-13 19:44:58 Re: global / super barriers (for checksums)
Previous Message Tom Lane 2019-11-13 19:31:39 Re: Creating foreign key on partitioned table is too slow