Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jYJdv-0004m5-PH for pgsql-hackers@arkaria.postgresql.org; Tue, 12 May 2020 01:23:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jYJdu-0008OR-Im for pgsql-hackers@arkaria.postgresql.org; Tue, 12 May 2020 01:23:34 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jYJdu-0008Nl-BT for pgsql-hackers@lists.postgresql.org; Tue, 12 May 2020 01:23:34 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jYJdr-000683-PY for pgsql-hackers@postgresql.org; Tue, 12 May 2020 01:23:33 +0000 Received: from bruce by momjian.us with local (Exim 4.92) (envelope-from ) id 1jYJdq-0004o8-Ag; Mon, 11 May 2020 21:23:30 -0400 Date: Mon, 11 May 2020 21:23:30 -0400 From: Bruce Momjian To: Peter Geoghegan Cc: PostgreSQL-development Subject: Re: PG 13 release notes, first draft Message-ID: <20200512012330.GS4666@momjian.us> References: <20200505031600.GB21752@momjian.us> <20200511231000.GC4666@momjian.us> <20200512001401.GG4666@momjian.us> <20200512011543.GR4666@momjian.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200512011543.GR4666@momjian.us> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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 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 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 +