| From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
|---|---|
| To: | "Burgess, Freddie" <FBurgess(at)Radiantblue(dot)com>, "PostgreSQL Bugs [pgsql-bugs(at)postgresql(dot)org]" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: Postgresql 9.3.4 Streaming Replication Standby invalid Page block |
| Date: | 2014-07-02 11:02:27 |
| Message-ID: | 53B3E6C3.40003@vmware.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 07/02/2014 02:03 AM, Burgess, Freddie wrote:
> PostgreSQL version: 9.3.4
> Operating system: rhel 6.4 linux
> Action: stream replication Master/Slave
> Description:
>
> Last entries in the PostgreSQL log file before the standby crashed, the primary seems unaffected
>
> LOG: restored log file "0000000100001127000000cc" from archive
> FATAL: invalid page in block 464698 of relation pg_tblspc/16435/PG_9.3_201306121/16444/125127698
> CONTEXT: xlog redo vacuum: rel 16435/16444/125127698; blk 512019, lastBlockVacuumed 0
> LOG: startup process (PID 27797) exited with exit code 1
> LOG: terminating any other active server processes
>
> We did re-started the database and the process of restoring the log file has continued beyond this point, but is are standby server corrupted?
Sounds exactly like this bug:
but that was fixed in 9.3.3 already. Are you sure you're running 9.3.4
in the standby too?
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-07-02 11:09:44 | Re: Postgresql 9.3.4 Streaming Replication Standby invalid Page block |
| Previous Message | Fujii Masao | 2014-07-02 06:58:08 | Re: BUG #10822: "ALTER SYSTEM cannot run inside a transaction block" when having autocommit disabled. |