From: Bruce Momjian <bruce@momjian.us>
To: Peter Geoghegan <pg@bowt.ie>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: PG 13 release notes, first draft
Date: Mon, 11 May 2020 21:23:30 -0400
Message-ID: <20200512012330.GS4666@momjian.us> (raw)
In-Reply-To: <20200512011543.GR4666@momjian.us>
References: <20200505031600.GB21752@momjian.us>
<CAH2-Wzmb1y8thdyspq2U8tput2SKrsSZLC2FSVfJxEPPtXrYoA@mail.gmail.com>
<20200511231000.GC4666@momjian.us>
<CAH2-Wzm7DmvZ7Ee99Fp-gqEY45yaA1PwDfacEBqS45F=h3sMAw@mail.gmail.com>
<20200512001401.GG4666@momjian.us>
<CAH2-WzknYzW14E=38Ht976VEYSDCDz11KyQ6woSEnVnkMDEX-g@mail.gmail.com>
<20200512011543.GR4666@momjian.us>
On Mon, May 11, 2020 at 09:15:43PM -0400, Bruce Momjian wrote:
> On Mon, May 11, 2020 at 05:33:40PM -0700, Peter Geoghegan wrote:
> > On Mon, May 11, 2020 at 5:14 PM Bruce Momjian <bruce@momjian.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.
>
> I still don't think these details belong in the release notes.
OK, I was able to add some of it cleanly:
This allows efficient btree indexing of low cardinality columns by
storing duplicate keys only once. Users upgrading with pg_upgrade
will need to use REINDEX to make use of this feature.
--
Bruce Momjian <bruce@momjian.us> https://momjian.us
EnterpriseDB https://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: bruce@momjian.us, pg@bowt.ie
Subject: Re: PG 13 release notes, first draft
In-Reply-To: <20200512012330.GS4666@momjian.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox