| From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us>, David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | "pgsql-bugs(at)postgresql(dot)org" <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-10 21:07:36 |
| Message-ID: | 1410383256.26571.YahooMailNeo@web122302.mail.ne1.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> On Sat, Sep 6, 2014 at 11:07:43AM -0400, 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.
>
> Applied, though I used the term "streaming standbys" to match our docs.
Hmm. The wording of the warning doesn't seem to really indicate
the full scope of the limitation. Any a standby (warm or hot)
maintained by WAL file copying would also be affected (i.e.,
streaming replication as the WAL delivery mechanism is irrelevant),
and you also have problems after a database crash or PANIC. I'm
not sure how to state that concisely, though.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2014-09-10 21:13:51 | Re: Re: BUG #10329: Could not read block 0 in file "base/56100265/57047884": read only 0 of 8192 bytes |
| Previous Message | Bruce Momjian | 2014-09-10 20:55:11 | Re: Re: BUG #10329: Could not read block 0 in file "base/56100265/57047884": read only 0 of 8192 bytes |