On Thu, Jan 2, 2014 at 11:59 AM, Christophe Pettus <xof@thebuild.com> wrote:
> In both cases, the indicated relation was a primary key index. In one case, rebuilding the primary key index caused
theproblem to go away permanently (to date). In the second case, the problem returned even after a full dump / restore
ofthe master database (that is, after a dump / restore of the master, and reimaging the secondary, the problem returned
atthe 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@mail.gmail.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.ru@gmail.com