From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | pgsql-committers <pgsql-committers(at)postgresql(dot)org> |
Subject: | Re: pgsql: hash: Add write-ahead logging support. |
Date: | 2017-03-14 18:18:07 |
Message-ID: | 7706.1489515487@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Tue, Mar 14, 2017 at 1:54 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Robert Haas <rhaas(at)postgresql(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2017-03-14 18:22:27 | Re: pgsql: hash: Add write-ahead logging support. |
Previous Message | Robert Haas | 2017-03-14 17:56:47 | Re: pgsql: hash: Add write-ahead logging support. |