Re: bumping HASH_VERSION to 3
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: Noah Misch <noah@leadboat.com>, Bruce Momjian <bruce@momjian.us>,
Tom Lane <tgl@sss.pgh.pa.us>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2017-05-19T20:54:27Z
Lists: pgsql-hackers
On Tue, May 16, 2017 at 9:25 AM, Amit Kapila <amit.kapila16@gmail.com> wrote: > On Tue, May 16, 2017 at 5:14 PM, Robert Haas <robertmhaas@gmail.com> wrote: >> On Tue, May 16, 2017 at 7:31 AM, Amit Kapila <amit.kapila16@gmail.com> wrote: >>> I will send an updated patch once we agree on above points. >> >> Sounds good. > > Attached patch addresses all the comments as discussed. Committed. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Commits
-
pg_upgrade: Handle hash index upgrades more smoothly.
- a95410e2ec39 10.0 landed
-
Expand hash indexes more gradually.
- ea69a0dead51 10.0 landed
-
Cache hash index's metapage in rel->rd_amcache.
- 293e24e50783 10.0 cited