| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | 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-08 13:45:02 |
| Message-ID: | 20140908134502.GB13690@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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. :-)
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | m.winkel | 2014-09-08 14:49:13 | BUG #11381: Inherited NOT NULL to NULLABLE column: backup restore error. |
| Previous Message | Michael Paquier | 2014-09-08 07:01:57 | Re: BUG #11353: Documentation for SET AUTOCOMMIT is wrong |