On Wed, Jun 9, 2021 at 12:14 PM Dilip Kumar <dilipbalaut@gmail.com> wrote:
>
> On Wed, Jun 9, 2021 at 2:07 AM Robert Haas <robertmhaas@gmail.com> wrote:
> 2021-06-09 12:11:08.618 IST [122456] LOG: entering standby mode
> 2021-06-09 12:11:08.622 IST [122456] LOG: restored log file "00000002.history" from archive
> cp: cannot stat
‘/home/dilipkumar/work/PG/postgresql/src/test/recovery/tmp_check/t_025_stuck_on_old_timeline_primary_data/archives/000000010000000000000002’:
Nosuch file or directory
> 2021-06-09 12:11:08.627 IST [122456] LOG: redo starts at 0/2000028
> 2021-06-09 12:11:08.627 IST [122456] LOG: consistent recovery state reached at 0/3000000
>
> Next, I will investigate, without a fix on v11 (maybe v12, v10..) why it is not hitting the defect location at all.
Andafter that, I will check the status on other older versions.
Reason for the problem was that the "-Xnone" parameter was not
accepted by "sub backup" in PostgresNode.pm so I created that for
backpatch. With attached patches I am to make it pass in v12,v11,v10
(with fix) and fail (without fix). However, we will have to make some
change for 9.6 because pg_basebackup doesn't support -Xnone on 9.6,
maybe we can delete the content from pg_wal after the backup, if we
think that approach looks fine then I will make the changes for 9.6 as
well.
Note: for param backport for v12 and v11 same patch getting applied
but for v10 due to some conflict we need a separate patch (both
attached).
--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com
