> On Jun 28, 2018, at 10:36 AM, Andres Freund <andres@xxxxxxxxxxx> wrote: > > How are you making the inference that that's the problem? It could very > well be a postgres bug or somebody having used pg_resetxlog or.. ? There could always be a postgres bug, however misconfigured cache layers are a very common cause of this kind of symptom, and postgres bugs very rare. I don't believe pg_resetxlog would cause this particular problem. Failure to recovery yes, but not illegal memory operation.
