| From: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Re: BUG #10329: Could not read block 0 in file "base/56100265/57047884": read only 0 of 8192 bytes |
| Date: | 2014-09-11 17:25:13 |
| Message-ID: | 5411DAF9.4040003@kaltenbrunner.cc |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 09/08/2014 03:45 PM, Bruce Momjian wrote:
> On Sat, Sep 6, 2014 at 09:42:45PM -0400, Alvaro Herrera wrote:
>> Bruce Momjian wrote:
>>
>>> Here is a patch which implements the warning during CREATE INDEX ...
>>> HASH. If WAL-logging of hash indexes is ever implemented, we can remove
>>> this warning.
>>
>> I think we should have CREATE UNLOGGED INDEX, and simply disallow any
>> hash index from being created unless it's marked as such.
>
> Wow, that sounds much more radical than we discussed. Seeing I got
> push-back just for the warning, I don't see how disabling "logged" WAL
> indexes is going to be accepted.
>
> It is a good idea, though. :-)
I agree there - implementing CREATE UNLOGGED INDEX and use THAT for hash
indexes seems like a fairly clean thing to me, hash indexes _are_
unlogged so lets reflect that directly.
I could even envision pg_dump doing that conversion automatically...
Stefan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-09-11 17:29:23 | Re: Re: BUG #10329: Could not read block 0 in file "base/56100265/57047884": read only 0 of 8192 bytes |
| Previous Message | Alvaro Herrera | 2014-09-11 14:37:18 | Re: BUG #11397: enable-profiling hangs configure at thread safety checking |