At Thu, 28 Oct 2021 13:52:36 +, "Ryan, Les" wrote in
> Hi Kyotaro and Dilip,
>
> Thank you for getting back to me.
>
> Kyotaro: I ran pg_dump and the output was "pg_waldump: fatal: could not read
> file "00010419005A": read 50 of 8192". I'm guessing that it
> means that wal f
you both for your help.
Sincerely,
-Les
-Original Message-
From: Dilip Kumar
Sent: October 27, 2021 10:29 PM
To: Kyotaro Horiguchi
Cc: Ryan, Les ; pgsql-generallists.postgresql.org
Subject: Re: WAL File Recovery on Standby Server Stops Before End of WAL Files
On Thu, Oct 28, 2021 at 7:2
On Thu, Oct 28, 2021 at 7:28 AM Kyotaro Horiguchi
wrote:
>
> At Wed, 27 Oct 2021 16:42:52 +, "Ryan, Les" wrote in
> > 2021-10-27 10:26:31.467 MDT [2012] LOG: redo starts at 419/5229A858
> ...
> > 2021-10-27 10:26:36.188 MDT [2012] LOG: restored log file
> > "00010419005A" from
At Wed, 27 Oct 2021 16:42:52 +, "Ryan, Les" wrote in
> 2021-10-27 10:26:31.467 MDT [2012] LOG: redo starts at 419/5229A858
...
> 2021-10-27 10:26:36.188 MDT [2012] LOG: restored log file
> "00010419005A" from archive
> 2021-10-27 10:26:36.750 MDT [2012] LOG: consistent recover
Hello,
I'm hoping to get some suggestions on what to do here. I am running PostgreSQL
version 13.2 and am shipping the WAL files to a standby server. Once a day I
restart the standby server and it recovers the new WAL files that have been
shipped to it. Everything was working great until yes
