Re: PG 13 release notes, first draft

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PG 13 release notes, first draft
Date: 2020-05-12 00:33:40
Message-ID: CAH2-WzknYzW14E=38Ht976VEYSDCDz11KyQ6woSEnVnkMDEX-g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, May 11, 2020 at 5:14 PM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Agreed. How is this?
>
> This allows efficient btree indexing of low cardinality columns.
> Users upgrading with pg_upgrade will need to use REINDEX to make use of
> this feature.

I still think that the release notes should say that the key is only
stored once, while TIDs that identify table rows are stored together
as an array. Everything that's helpful (or harmful) about the feature
happens as a consequence of that. This isn't hard to grasp
intuitively, and is totally in line with how things like Oracle bitmap
indexes are presented to ordinary users.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2020-05-12 00:34:15 Re: PG 13 release notes, first draft
Previous Message Bruce Momjian 2020-05-12 00:33:31 Re: PG 13 release notes, first draft (ltree dot star)