From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
cc: pgsql-committers <pgsql-committers@postgresql.org>
Subject: Re: pgsql: hash: Add write-ahead logging support.
In-reply-to: 
 <CA+TgmoZ7hPabY=+PH47iiDjRvUJ5eZyvXKFnNzfbGrRJp-w9xA@mail.gmail.com>
References: <E1cnqE2-0008JV-Uv@gemulon.postgresql.org>
 <5515.1489514099@sss.pgh.pa.us>
 <CA+TgmoZ7hPabY=+PH47iiDjRvUJ5eZyvXKFnNzfbGrRJp-w9xA@mail.gmail.com>
Comments: In-reply-to Robert Haas <robertmhaas@gmail.com>
	message dated "Tue, 14 Mar 2017 13:56:47 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <7705.1489515487.1@sss.pgh.pa.us>
Date: Tue, 14 Mar 2017 14:18:07 -0400
Message-ID: <7706.1489515487@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-committers-owner@postgresql.org

Robert Haas <robertmhaas@gmail.com> writes:
> On Tue, Mar 14, 2017 at 1:54 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Robert Haas <rhaas@postgresql.org> 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.

You gonna do it, or you want me to?

			regards, tom lane


-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers