Re: hash index on unlogged tables doesn't behave as expected
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Noah Misch <noah@leadboat.com>
Cc: Amit Kapila <amit.kapila16@gmail.com>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2017-07-08T03:11:06Z
Lists: pgsql-hackers
On Wed, Jul 5, 2017 at 11:02 PM, Noah Misch <noah@leadboat.com> wrote: > [Action required within three days. This is a generic notification.] > > The above-described topic is currently a PostgreSQL 10 open item. Robert, > since you committed the patch believed to have created it, you own this open > item. If some other commit is more relevant or if this does not belong as a > v10 open item, please let us know. Otherwise, please observe the policy on > open item ownership[1] and send a status update within three calendar days of > this message. Include a date for your subsequent status update. Testers may > discover new open items at any time, and I want to plan to get them all fixed > well in advance of shipping v10. Consequently, I will appreciate your efforts > toward speedy resolution. Thanks. I don't intend to rush this in before the beta2 wrap, although some other committer is welcome to do so if they feel confident in the fix. I will update again by July 17th. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Commits
-
hash: Fix write-ahead logging bugs related to init forks.
- 09c2e7cd2ff0 10.0 landed
-
Issue a warning during the creation of hash indexes
- 84aa8ba128a0 9.5.0 cited