From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
---|---|
To: | Thom Brown <thom(at)linux(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Hash index creation warning |
Date: | 2015-06-23 00:06:33 |
Message-ID: | 5588A309.50301@BlueTreble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 6/12/15 5:00 PM, Thom Brown wrote:
> On 18 October 2014 at 15:36, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>> On Fri, Oct 17, 2014 at 02:36:55PM -0400, Bruce Momjian wrote:
>>> On Fri, Oct 17, 2014 at 12:56:52PM -0400, Tom Lane wrote:
>>>> David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
>>>>> The question is whether we explain the implications of not being WAL-logged
>>>>> in an error message or simply state the fact and let the documentation
>>>>> explain the hazards - basically just output:
>>>>> "hash indexes are not WAL-logged and their use is discouraged"
>>>>
>>>> +1. The warning message is not the place to be trying to explain all the
>>>> details.
>>>
>>> OK, updated patch attached.
>>
>> Patch applied.
>
> I only just noticed this item when I read the release notes. Should
> we bother warning when used on an unlogged table?
Not really; but I think the bigger question at this point is if we want
to change it this late in the game.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Data in Trouble? Get it in Treble! http://BlueTreble.com
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2015-06-23 00:19:19 | Re: less log level for success dynamic background workers for 9.5 |
Previous Message | Jim Nasby | 2015-06-22 23:56:35 | Re: proposal: row_to_array function |