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.
Date: Tue, 14 Mar 2017 14:18:07 -0400
Message-ID: <7706.1489515487@sss.pgh.pa.us> (raw)
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>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-committers>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: tgl@sss.pgh.pa.us, robertmhaas@gmail.com
Subject: Re: pgsql: hash: Add write-ahead logging support.
In-Reply-To: <7706.1489515487@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox