On Tue, Mar 14, 2017 at 11:26 PM, Robert Haas <[email protected]> wrote: > On Tue, Mar 14, 2017 at 1:54 PM, Tom Lane <[email protected]> wrote: >> Robert Haas <[email protected]> writes: >>> hash: Add write-ahead logging support. >> >> This bit in access/hash/README, lines 368ff, appears obsolete: >> >> Although we can survive a failure to split a bucket, a crash is likely to >> corrupt the index, since hash indexes are not yet WAL-logged. >> >> Perhaps we can just delete that para. If not, what should it say now? > > That's obsolete, and can just be removed. >
Agreed and posted a patch on hackers [1] [1] - https://www.postgresql.org/message-id/CAA4eK1LeVu8rSvA%3DhfbezqjNv5x3nU-rPbHCHHbbsCrLX-0zAg%40mail.gmail.com -- With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
