| From: | Sergey Konoplev <gray(dot)ru(at)gmail(dot)com> |
|---|---|
| To: | Christophe Pettus <xof(at)thebuild(dot)com> |
| Cc: | PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Streaming replication bug in 9.3.2, "WAL contains references to invalid pages" |
| Date: | 2014-01-03 20:50:14 |
| Message-ID: | CAL_0b1vEaAP-u8joBuf1PFbFT_1WfZMhOm4k1jMaK36d3CZVxA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jan 2, 2014 at 11:59 AM, Christophe Pettus <xof(at)thebuild(dot)com> wrote:
> In both cases, the indicated relation was a primary key index. In one case, rebuilding the primary key index caused the problem to go away permanently (to date). In the second case, the problem returned even after a full dump / restore of the master database (that is, after a dump / restore of the master, and reimaging the secondary, the problem returned at the same primary key index, although of course with a different OID value).
>
> It looks like this has been experienced on 9.2.6, as well:
>
> http://www.postgresql.org/message-id/flat/CAL_0b1s4QCkFy_55kk_8XWcJPs7wsgVWf8vn4=jXe6V4R7Hxmg(at)mail(dot)gmail(dot)com
This problem worries me a lot too. If someone is interested I still
have a file system copy of the buggy cluster including WAL.
--
Kind regards,
Sergey Konoplev
PostgreSQL Consultant and DBA
http://www.linkedin.com/in/grayhemp
+1 (415) 867-9984, +7 (901) 903-0499, +7 (988) 888-1979
gray(dot)ru(at)gmail(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Omar Kilani | 2014-01-03 21:40:56 | Re: Streaming replication bug in 9.3.2, "WAL contains references to invalid pages" |
| Previous Message | Fabien COELHO | 2014-01-03 17:53:49 | Re: ISN extension bug? (with patch) |