On Thu, Jan 2, 2014 at 11:59 AM, Christophe Pettus <x...@thebuild.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:
This problem worries me a lot too. If someone is interested I still
have a file system copy of the buggy cluster including WAL.
PostgreSQL Consultant and DBA
+1 (415) 867-9984, +7 (901) 903-0499, +7 (988) 888-1979
Sent via pgsql-hackers mailing list (email@example.com)
To make changes to your subscription: