| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Jakub Ouhrabka <kuba(at)comgate(dot)cz> |
| Cc: | pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: Corrupted index on 9.0.3 streaming hot standby |
| Date: | 2011-02-25 15:53:57 |
| Message-ID: | 1298649207-sup-4689@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Excerpts from Jakub Ouhrabka's message of vie feb 25 08:20:33 -0300 2011:
> For details about corrupted index see below. The table and index in
> question are mostly read-only (several queries per second) writes happen
> only few times a day.
>
> We've backed up whole cluster and recreated it.
>
> Shall we investigate it further? How? Is it possible that we make some
> mistake when doing initial backup which caused corruption? Is there a
> way to check other indexes?
Do you still have the WAL files?
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2011-02-25 16:03:13 | Re: BUG #5899: Memory corruption when running psql |
| Previous Message | Merlin Moncure | 2011-02-25 15:48:50 | Re: Function trunc() behaves in unexpected manner with different data types |