From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Daniel Farina <daniel(at)citusdata(dot)com> |
Cc: | Peter Geoghegan <pg(at)bowt(dot)ie>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: BUG #15745: WAL References Invalid Pages...that eventually resolves |
Date: | 2019-05-07 03:34:22 |
Message-ID: | 20190507033422.GI1499@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Sun, May 05, 2019 at 08:37:02PM -0700, Daniel Farina wrote:
> Regrettably, it's too late, but I'll have my notes for next time.
Here is a guess: the base backup which has been used for this
instance's recovery has been taken from a standby, where the
minimum recovery LSN registered in its control file did not actually
map to the last physical LSN where a page has been flushed by either
the checkpointer, the startup process or a read-only backend.
This reminds me of the problems between 3c64dcb and c186ba1 I was at
the origin of, but this refers to 11.1, which was released after the
fact. Or perhaps a beta version of 11 has been used?
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2019-05-07 03:37:45 | Re: BUG #15791: WalSndCtl->sync_standbys_defined modified too late |
Previous Message | PG Bug reporting form | 2019-05-07 00:51:04 | BUG #15792: Dependency remains on foreign key constraint when child detached from declarative partition. |