Skip to main content

Hello,

We have a PG instance that failed to backup for a day due to an issue with our archive script.  We fixed the script, and CV ran and immediately picked up all the logs.

However, in the GUI, it’s still showing a gap in recovery; from the time the archiver originally failed, until the time it picked them up.

I haven’t been able to test a restore to a time during the gap yet (I hope to today), but I was able to click a missing recovery point and the API scripts accepts the time I chose.

Is this a bug in the GUI or something else?

Thanks!

Hi @Chris Newman ,

We should be able to recover to the timestamp in the gap as long as we backed up all logs after fixing archive_command. However, the UI might still show as no recovery points during that time, but the bar indicates the PIT recovery.

If this is not what you’re trying to explain and I’m not understanding your issue correctly, a screenshot would help.

 

Thanks,

Sunil-

 

 


Hi @Sunil ,

Thank you.  You nailed it, the GUI doesn’t show the PITR, but you can certainly do a pitr if you’ve got the logs, CV is aware of them, just not showing those restore points in the GUI.

 

time=2024-10-04 08:55:08 CDT, pid=2306114 LOG:  restored log file "00000001000002CB0000003F" from archive
time=2024-10-04 08:55:08 CDT, pid=2306114 LOG:  recovery stopping before commit of transaction 92175643, time 2024-10-04 03:58:46.751639-05

 

Awesome, thanks again!

 

  • Chris

Hi @Sunil ,

Thank you.  You nailed it, the GUI doesn’t show the PITR, but you can certainly do a pitr if you’ve got the logs, CV is aware of them, just not showing those restore points in the GUI.

 

time=2024-10-04 08:55:08 CDT, pid=2306114 LOG:  restored log file "00000001000002CB0000003F" from archive
time=2024-10-04 08:55:08 CDT, pid=2306114 LOG:  recovery stopping before commit of transaction 92175643, time 2024-10-04 03:58:46.751639-05

 

Awesome, thanks again!

 

  • Chris

Cool.. thanks for the revert.


Reply